Website review, no card needed

worlds.io logo

worlds.io website review

Visit site (opens in a new tab)Reviewed 22 October 202635 issues · 81 checks

This review found 35 issues worth fixing on worlds.io, 15 of them high impact, across 81 checks. The most urgent: improve image delivery. 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
4.6 s2.9 sMay 2Oct 174.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.3 s
May 9, 20263.8 s
May 16, 20263.1 s
May 23, 20263.7 s
May 30, 20263.7 s
Jun 6, 20263.7 s
Jun 13, 20263.8 s
Jun 20, 20263.8 s
Jun 27, 20264.3 s
Jul 4, 20264.4 s
Jul 11, 20264.4 s
Jul 18, 20264.4 s
Jul 25, 20264.3 s
Aug 1, 20264.0 s
Aug 8, 20264.4 s
Aug 15, 20264.3 s
Aug 22, 20264.0 s
Aug 29, 20264.0 s
Sep 5, 20264.1 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20263.9 s
Oct 3, 20264.0 s
Oct 10, 20264.2 s
Oct 17, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
126 ms89 msMay 23Oct 17119 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026120 ms
May 30, 2026117 ms
Jun 6, 2026117 ms
Jun 13, 2026117 ms
Jun 20, 2026110 ms
Jun 27, 202697 ms
Jul 4, 2026106 ms
Jul 11, 2026107 ms
Jul 18, 2026107 ms
Jul 25, 2026107 ms
Aug 1, 202693 ms
Oct 3, 2026122 ms
Oct 10, 2026116 ms
Oct 17, 2026119 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 worlds.io (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix45
  • Improve image delivery

    11.8 s · 3.7 MB

    2 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.8 s faster on a phone.

  • Reduce unused JavaScript

    2.4 s · 466 KiB

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

  • Reduce unused CSS

    1.6 s · 129 KiB

    About 129 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Render-blocking requests

    1.5 s

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45 (desktop: 54). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Squarespace, Google Tag Manager and Hubspot and others), adding 1.6 MB and 1.1 s of main-thread time.

  • Squarespace adds 813 ms

    813 ms

    Squarespace costs a phone 813 ms of main-thread work and 1.1 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Legacy JavaScript

    300 ms · 125 KiB

    Polyfills for old browsers add 125 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 3.4 s

    A phone's processor spends 3.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 long tasks on the main thread

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

  • Use efficient cache lifetimes

    136 KiB

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

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

1 checks passed
  • Server response: 33 ms

    33 ms

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

Core Web Vitals

11 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Real-user LCP: 4.5 s

    4.5 s

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

  • Largest Contentful Paint: 27.8 s

    27.8 s

    Your largest element takes 27.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Operational AI for the Physical World”.

  • Time to Interactive: 27.8 s

    27.8 s

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

  • First Contentful Paint: 5.5 s

    5.5 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • Largest content (LCP) got 20% slower for real visitors

    +20%

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

  • Real-user FCP: 3.0 s

    3.0 s

    Real visitors see the first content after 3.0 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.

  • Total Blocking Time: 483 ms

    483 ms

    Scripts block taps and scrolling for 483 ms in total while the page loads. Good is under 200 ms.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -1%

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

3 checks passed
  • Real-user INP: 128 ms

    128 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix48
  • Page weight: 6.4 MB in 102 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 102 requests on a phone: images 4.5 MB (9), scripts 1.3 MB (62) and fonts 296 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    newHero2.png weighs 932 KiB. On a phone connection a single image that size takes seconds.

  • 3 images below the first screen load straight away

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

  • About 1.8 g of CO₂ per visit

    1.81 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

Google 98100
  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

5 to fixGoogle 8572
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (6 characters)

    Your title is only 6 characters: “Worlds”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Operational AI for the Physical World”, “Turn physical operations into real-time spatial i…” and “30-50%”). One clear main headline is easier for people and search engines.

  • Structured data has 2 problems

    Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/65c166911f637f001c5…”.

  • 2 links with vague text

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 27 internal links, 9 external

    The homepage links to 27 pages on worlds.io and 9 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.worlds.io/.

  • 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.worlds.io/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (0 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 8 pages without a meta description

    https://www.worlds.io/platform/worlds, https://www.worlds.io/about, https://www.worlds.io/careers, https://www.worlds.io/contact, https://www.worlds.io/case-study-metallus and https://www.worlds.io/terms-of-use and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages with very little text

    https://www.worlds.io/careers and https://www.worlds.io/contact have 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.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 9 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • 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 9 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/65c166911f637f001c5e836b/255/5c5…”.

2 checks passed
  • Tap targets are thumb-sized

    6 of 6 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 423 words of copy

    The homepage carries about 423 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: “Learn more”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”, “Learn more” and “Contact Sales”.

  • Analytics in place

    Analytics detected: Google Analytics and HubSpot.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and HubSpot (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 worlds.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Squarespace
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 35 issues on worlds.io, including 20 speed issues, 5 SEO issues and 3 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