storybug.com website review

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

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

25 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

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

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

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

Shopify costs a phone 50 ms of main-thread work and 330 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.

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

4 third-party services load with your homepage (Shopify, Trust Pilot and Google Fonts and others), adding 419 KiB and 91 ms of main-thread time.

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

Polyfills for old browsers add 7 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.

2 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

3 images weigh 11.5 MB together. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example home-zoo-scene.webp at 3,200 px wide, shown at 937 px. Resized copies would save about 3.8 MB.

8 images (12.4 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.

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

Your homepage downloads 3.5 MB in 213 requests on a phone: images 1.9 MB (29), other files 742 KiB (91) and scripts 643 KiB (52). Under 2 MB keeps phones on slow connections fast.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

There are 2 <h1> headlines (“” and “Fully Custom Books for Your Loved Ones!”). One clear main headline is easier for people and search engines.

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

The homepage links to 108 pages on storybug.com and 10 external pages.

Your Organization JSON-LD is missing logo, 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.

https://www.storybug.com/pages/shipping has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

The homepage carries about 536 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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 18 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.