What customers see first after tapping a review link on a phone (2026 test)

We opened review links for GetRating, Google, Trustpilot and Facebook 60 times on an emulated phone with a slow 4G connection, logged out, from Norway, and recorded the first screen each one showed and how long it took. Test run 28 October 2026.

By GetRating team, Getia AS. Last checked .

Key findings

  • Google: in all 15 loads, a logged-out visitor who opened a Google write-review link landed on the Google sign-in page (accounts.google.com, after 2 redirects), in a median 1.2 seconds. The review form is only reachable with a Google account.
  • Trustpilot: the review page showed its star picker after a median 9.2 seconds (range 8.9–9.4 s), with a cookie notice on every load. Trustpilot does not ask for sign-in before the first star.
  • Facebook: the reviews tab opened with a full-screen cookie choice dialog in all 15 loads, after a median 1.7 seconds. No review option was visible before the visitor answers it.
  • GetRating: the rating screen showed five tappable stars after a median 3.4 seconds (range 3.3–3.5 s), with no redirect. A cookie notice was shown at the bottom of the screen on every load; it does not cover the stars.
  • Tripadvisor blocked our automated browser on the test day, so it is not measured.

Results by platform

GetRatingStar rating3.4 sGoogleGoogle sign-in1.2 sTrustpilotStar rating9.2 sFacebookCookie choice dialog1.7 s
Median time until the first usable screen, slow 4G phone profile, 60 loads, 2026-10-28. Shorter is faster.
First screen after opening a review link, logged out, Norway, 2026-10-28.
PlatformFirst screenMedian (range)RedirectsCookie notice
GetRatingStar rating3.4 s (3.3 s–3.5 s)015 of 15 loads
GoogleGoogle sign-in1.2 s (1.2 s–1.3 s)20 of 15 loads
TrustpilotStar rating9.2 s (8.9 s–9.4 s)015 of 15 loads
FacebookCookie choice dialog1.7 s (1.3 s–5.5 s)015 of 15 loads

Tripadvisor is missing because it blocked the automated browser on the test day.

What the GetRating screen looks like

GetRating rating page on a phone asking How was your experience? with five star buttons
What a customer sees after scanning the QR code: the business name, one question and five stars. No app or account is needed.

Screenshots are taken from the live GetRating dashboard, logged in to a GetRating test account that holds test data only. Captured .

What this means for asking customers for reviews

  • Google reviews need a Google account. Customers who are signed in on their phone skip the sign-in page; others have to sign in or create an account first. Offer a second review site so those customers have another option.
  • Trustpilot needs no sign-in to start, but its page took about 9 seconds to become usable on a slow connection. Ask at a moment when the customer has time, for example by email or SMS after the visit.
  • Facebook shows a cookie dialog before anything else in Norway, so a Facebook review link costs the customer an extra decision.
  • A GetRating page is one extra screen before the review site. It lets customers rate you and pick from all your review links; it does not remove the sign-in on the review site. How the modes work: review modes guide.

Method

  • Browser: Playwright with Chromium headless shell, emulating a Pixel 8 (Android user agent, 412 × 915 screen, touch), Norwegian locale and Oslo time zone, from a broadband connection in Oslo, Norway.
  • Network and CPU throttled to the slow 4G profile Lighthouse uses: 150 ms latency, 1.6 Mbit/s down, 750 kbit/s up, CPU slowed 4×.
  • Every load used a fresh browser profile: logged out, no cookies. 3 links per platform, 5 loads per link, 60 loads in total.
  • Links: GetRating review pages of 3 GetRating test locations; Google write-review links (search.google.com/local/writereview) for 3 place IDs taken from Google's developer documentation; Trustpilot review pages (/evaluate) for elkjop.no, komplett.no and zalando.no; the Facebook reviews tab of the IKEA Norge, Elkjøp and Norwegian pages.
  • "First screen ready" is the time from starting the navigation until the first usable element was visible, checked every 100 ms: GetRating's five star buttons, Trustpilot's five star inputs, Google's sign-in field, and Facebook's cookie dialog buttons.
  • Nothing was submitted on any site. The script and the raw data for every load are published below.
  • After a short pilot, the full 60-load test was run twice that morning and the second run is published. The first run showed the same first screen on every load and medians within 0.2 seconds of these (GetRating 3.4 s, Google 1.2 s, Trustpilot 9.2 s, Facebook 1.8 s). A later re-run of the published script the same day gave 3.3 s, 1.2 s, 9.3 s and 1.6 s.
  • The script also logs transfer size and request count. They are left out of the data because the counter recorded 0 KB for every Google load, which ends on another host after 2 redirects, so the figures are not comparable across platforms.

Limitations

  • Logged-out visitors only. A customer who is already signed in to Google on their phone usually skips the sign-in page; we did not test that.
  • A headless browser can be treated differently from a real phone, and emulated throttling is not a real mobile network.
  • One country (Norway), one day, 15 loads per platform. Pages and consent rules differ by country and change over time.
  • This measures the first screen, not the time to a finished review. GetRating's page is an extra step before the review site, not a replacement for it: after the rating, the customer still goes to Google or the other site and meets its sign-in.
  • The GetRating pages are our own test locations without a logo, so they are lighter than many real pages.

Download the data

  • Raw data (CSV): one row per load: platform, link, load number, first screen, time, redirects, final host, cookie notice
  • Measurement script: run it with node measure.mjs targets.json 5 results.json after installing playwright-core and Chromium
  • Links tested: the 12 links used, 3 per platform

Published under CC BY 4.0. Cite as: GetRating (2026), “What customers see first after tapping a review link on a phone (2026 test)”, https://getrating.co/research/review-link-first-screen-2026.

Frequently asked questions

Do customers need a Google account to leave a Google review?

Yes. In our test every logged-out visitor who opened a Google write-review link was sent to the Google sign-in page first. Customers who are already signed in to Google on their phone usually go straight to the review form.

How long does a review page take to load on a slow mobile connection?

On a slow 4G phone profile, Trustpilot's star picker took a median 9.2 seconds and GetRating's rating screen 3.4 seconds. Google's sign-in page appeared in 1.2 seconds, and Facebook showed a cookie dialog after 1.7 seconds.

Does a GetRating page make leaving a Google review faster?

No. It adds one screen before the review site, so customers can rate you and see all your review links. The Google sign-in that logged-out customers meet still comes after it.

Ask every customer for a review

Free plan for 1 location. No credit card required.

Start free