anything.world website review

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

14 files are served with short cache lifetimes, so returning visitors download them again (53.9 MB).

14 images could be 46.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, website-files.com and cloudfront.net and others), adding 21.2 MB and 1.1 s of main-thread time.

website-files.com costs a phone 338 ms of main-thread work and 20.8 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.

Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.

Google Tag Manager costs a phone 559 ms of main-thread work and 323 KiB 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.

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

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

About 243 KiB of JavaScript is downloaded but never used on this page.

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

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

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

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

5 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 65.9 MB in 66 requests on a phone: images 46.8 MB (31), media 18.2 MB (4) and scripts 711 KiB (13). Under 2 MB keeps phones on slow connections fast.

8 images weigh 44.5 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example aw_homepage_brain.gif at 1,080 px wide, shown at 338 px. Resized copies would save about 2.6 MB.

10 images (44.7 MB) are 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.

7 images further down the page (30.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

691cddfd86b34a0501fc5db8_everything_universe_name_small-p-50 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

12 visible links have no text or label, so screen readers cannot say where they go.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 16 pages on anything.world and 45 external pages.

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.

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.

/team, /powered-by-anything-world and /terms-of-use have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link to other sites is dead, for example https://assetstore.unity.com/packages/tools/animation/limitless-animated-3d-models-by-anything-world-261647 (404).

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

2 links go through two or more redirects, for example https://apps.autodesk.com/MAYA/en/Detail/Index?id=1892575614406902370&os=Win64.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

everythinguniver.se has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

The homepage carries about 268 words of visible text.

DMARC is set to p=none, so mail pretending to be anything.world is still delivered. Add a report address, check the reports, then move to quarantine.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 include:_mailcust.gandi.net include:7805117.spf03.hubspotemail.net ?all”.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Reddit Pixel and X (Twitter) Ads (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.

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

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.

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