speedtest.net website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 3.2 s

  3.2 s

  Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

• Real-user INP: 289 ms

  289 ms

  Real visitors wait 289 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

• Tap response (INP) got 59% slower for real visitors

  +59%

  Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 169 ms to 275 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Real-user FCP: 2.2 s

  2.2 s

  Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

• Real-user TTFB: 1.1 s

  1.1 s

  Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

• Page weight: 2.4 MB

  2.4 MB

  Your homepage downloads 2.4 MB on a phone, 78 KiB of it images (3%). Under 2 MB keeps phones on slow connections fast.

• 1 image in older formats

  1 image (45 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  Elements (1)

• About 0.7 g of CO₂ per visit

  0.68 g

  By the Sustainable Web Design model, a visit to your homepage emits about 0.68 g of CO₂e: 81.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

• 22 text elements with low contrast

  22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (3)

• ARIA dialog and alertdialog nodes should have an accessible name (1 element)

  ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• Headings skip levels

  Headings skip levels (h1 → h3 and h3 → h6), which makes the page harder to scan with a screen reader.

  View source

• No structured data

  No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

• 2 H1 headlines

  There are 2 <h1> headlines (“Speedtest by Ookla” and “GO”). One clear main headline is easier for people and search engines.

  View source

• 61 internal links, 20 external

  The homepage links to 61 pages on speedtest.net and 20 external pages.

• No Organization structured data

  There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

• No llms.txt

  There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

• 1 page points its canonical at the homepage

  /en declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  Elements (1)

• 6 pages share a title

  /, /en, /ar, /ja, /ko and /th all use the title “Speedtest by Ookla - The Global Broadband Speed Test”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (6)

• 5 pages share a meta description

  /en, /ar, /ja, /ko and /th use the same meta description. A description written for each page earns more clicks.

• 1 page with very little text

  /ru has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.

• 24 small tap targets

  24 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

• 3 JavaScript errors while loading

  3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://api.rlcdn.com/api/identity/envelope?pid=14461&gpp=DBABLA~BVQqAAAAAACA.QA&gpp_sid=7' from or…”.

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• Only about 135 words

  The homepage has only about 135 words of visible text; thin pages give Google and first-time buyers little to go on.

• No form on the homepage

  There is no form on the homepage, so every lead has to click through to another page first.

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• 5 trackers load before any consent

  5

  Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

• 14 cookies set on arrival

  14

  Opening the homepage sets 14 cookies (measured from a US location before any click).

• 44 other companies contacted

  Loading the homepage contacts 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.