pocketworlds.com website review

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

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

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

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

2 third-party services load with your homepage (Google Fonts and highrisegame.com), adding 7.0 MB and 0 ms of main-thread time.

highrisegame.com costs a phone 0 ms of main-thread work and 6.9 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.

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

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

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.

2 KiB could be saved by minifying CSS.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We build and grow”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 7.4 MB in 61 requests on a phone: images 7.4 MB (53), fonts 57 KiB (3) and stylesheets 15 KiB (2). Under 2 MB keeps phones on slow connections fast.

23 images are downloaded at several times the size a phone draws them, for example HR_01_EN.webp at 1,290 px wide, shown at 96 px. Resized copies would save about 2.7 MB.

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

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

Your title is only 29 characters: “Pocket Worlds | Play Forever.”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No XML sitemap at https://pocketworlds.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at pocketworlds.com/robots.txt, the first file search crawlers ask for.

The homepage links to 9 pages on pocketworlds.com and 10 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 https://pocketworlds.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.

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

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

Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 628 words of visible text.

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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.