Website review, no card needed

worldatlas.com logo

worldatlas.com website review

Visit site (opens in a new tab)Reviewed 11 October 202625 issues · 78 checks

This review found 25 issues worth fixing on worldatlas.com, 8 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.4 s997 msApr 18Oct 31.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.2 s
Apr 25, 20261.3 s
May 2, 20261.3 s
May 9, 20261.2 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.3 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
168 ms125 msApr 18Oct 3138 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026163 ms
Apr 25, 2026159 ms
May 2, 2026156 ms
May 9, 2026153 ms
May 16, 2026150 ms
May 23, 2026146 ms
May 30, 2026146 ms
Jun 6, 2026144 ms
Jun 13, 2026144 ms
Jun 20, 2026146 ms
Jun 27, 2026144 ms
Jul 4, 2026143 ms
Jul 11, 2026140 ms
Jul 18, 2026135 ms
Jul 25, 2026133 ms
Aug 1, 2026130 ms
Aug 8, 2026130 ms
Aug 15, 2026131 ms
Aug 22, 2026132 ms
Aug 29, 2026135 ms
Sep 5, 2026137 ms
Sep 12, 2026137 ms
Sep 19, 2026138 ms
Sep 26, 2026139 ms
Oct 3, 2026138 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of worldatlas.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. worldatlas.com at 0.4 s0.4 s
  2. worldatlas.com at 0.8 s0.8 s
  3. worldatlas.com at 1.1 s1.1 s
  4. worldatlas.com at 1.5 s1.5 s
  5. worldatlas.com at 1.9 s1.9 s
  6. worldatlas.com at 2.3 s2.3 s
  7. worldatlas.com at 2.6 s2.6 s
  8. worldatlas.com at 3.0 s3.0 s

Speed

4 to fix63
  • Reduce unused JavaScript

    1.1 s · 188 KiB

    About 188 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 100). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    546 KiB

    16 images could be 546 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2,012 HTML elements

    The page has 2,012 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, consentmanager.net and Mediavine and others), adding 657 KiB and 440 ms of main-thread time.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 105 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    83 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (83 KiB).

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

  • Phones get a much slower page than desktops

    Desktop scores 100 but mobile only 63. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 513 ms of it running JavaScript. That is comfortably low.

  • Server response: 20 ms

    20 ms

    Your server sent the HTML in 20 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 9.0 s

    9.0 s

    Your largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The Rocky Mountains in Jasper National Park, Alberta”.

  • First Contentful Paint: 3.6 s

    3.6 s

    The first text or image appears after 3.6 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 9.1 s

    9.1 s

    The page becomes fully interactive after 9.1 s. Good is under 3.8 s.

  • Speed Index: 5.8 s

    5.8 s

    Visually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.

10 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 141 ms

    141 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 484 ms

    484 ms

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

  • Tap response (INP) got 14% faster for real visitors

    -14%

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 125 ms

    125 ms

    Scripts block the page for only 125 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix68
  • Page weight: 2.3 MB in 88 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 88 requests on a phone: images 1.6 MB (46), scripts 648 KiB (25) and HTML 76 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 12 images below the first screen load straight away

    12 images further down the page (835 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 8 images far larger than shown

    237 KiB

    8 images are downloaded at several times the size a phone draws them, for example it-01.jpg at 649 px wide, shown at 170 px. Resized copies would save about 237 KiB.

  • About 0.7 g of CO₂ per visit

    0.66 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8991
  • Links must have discernible text (5 elements)

    Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.

  • Elements must only use permitted ARIA attributes (4 elements)

    Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (8 elements)

    All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 88 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9278
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (97 characters)

    Your title is 97 characters, so Google will cut it off around 60: “World Map / World Atlas / Atlas of the World Including Geography Facts and Flags - WorldA…”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 7 links with vague text

    7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 262 internal links, 34 external

    The homepage links to 262 pages on worldatlas.com and 34 external pages.

5 checks passed
  • Meta description: 112 characters

    Your meta description is 112 characters: “Well-researched and entertaining content on geography (including world maps), science, current events, and more.”.

  • Canonical URL set

    The canonical URL is https://www.worldatlas.com/.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.worldatlas.com/webmap/sitemap-index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.worldatlas.com/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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (651 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • 11 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • 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.

  • About 704 words of copy

    The homepage carries about 704 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 4 cookies set on arrival

    4

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

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 14 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at worldatlas.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on worldatlas.com, including 8 speed issues, 4 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25