getrocketbook.co.uk website review

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

18 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, rebuyengine.com and Shopify and others), adding 1.3 MB and 728 ms of main-thread time.

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

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

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

About 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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.

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.

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

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

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

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

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

The layout shifts by 0.108 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 5.4 MB in 289 requests on a phone: images 2.9 MB (44), scripts 1.5 MB (72) and other files 664 KiB (94). Under 2 MB keeps phones on slow connections fast.

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

8 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

[role="img"] and [role="image"] elements must have alternative text: 7 elements on the page fail this check, rated serious by axe-core.

6 tap targets are too small or too close together to hit reliably with a finger.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 element hidden from screen readers can still receive keyboard focus.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

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

38 links have no real href, so search engines can't follow them.

There are 4 <h1> headlines (“”, “Out of This World Productivity Awaits” and “The Rocketbook Advantage”). 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.

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

The homepage links to 67 pages on getrocketbook.co.uk and 18 external pages.

Your homepage links to https://getrocketbook.co/pages/about-rocketbook, which answers with an error. Visitors hit a dead end and search engines drop it.

https://getrocketbook.co/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://getrocketbook.co/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://getrocketbook.co/collections/accessories, https://getrocketbook.co/pages/how-rocketbook-works, https://getrocketbook.co/pages/faqs, https://getrocketbook.co/customer_authentication/redirect and https://getrocketbook.co/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://getrocketbook.co/products/new-rocketbook-core and https://getrocketbook.co/products/rocketbook-lined-notebook use the same meta description. A description written for each page earns more clicks.

https://getrocketbook.co/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://getrocketbook.co/customer_authentication/redirect and https://getrocketbook.co/products/rocketbook-lined-notebook took over 3 s to send their HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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 1,154 words of visible text.

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