therockfish.co.uk website review

4 images could be 368 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Klaviyo, Clarity and Feefo.com and others), adding 1.2 MB and 490 ms of main-thread time.

Klaviyo costs a phone 266 ms of main-thread work and 611 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 314 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

14 KiB could be saved by minifying CSS.

Desktop scores 91 but mobile only 64. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We’re on a mission to change the way people experience seaf…”.

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

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

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

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

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

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

Your homepage downloads 6.4 MB in 220 requests on a phone: images 4.2 MB (25), scripts 1.1 MB (99) and other files 608 KiB (61). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Dover-sole-Meuniere.jpg at 390 px wide, shown at 72 px. Resized copies would save about 139 KiB.

1 image further down the page (74 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 68 characters, so Google will cut it off around 60: “Rockfish Seafood Restaurants & Online Seafood Market - Fresh seafood”.

Your meta description is 305 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 207 pages on therockfish.co.uk and 9 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://therockfish.co.uk/pages/restaurant-menu/brixham and https://therockfish.co.uk/pages/takeaway-menu/brixham all use the title “Brixham – Rockfish”. Search engines can't tell which page to show for a search, so each competes with the others.

https://therockfish.co.uk/pages/allergens-menus and https://therockfish.co.uk/pages/rockfish-seafood-restaurants have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97272015&Ver=2&mid=c62e77ee-3f05-486e-90e3-886ba11c0204&bo=1&sid=da391500cf0c11f1a01db14a02d6634b&vid=da39a350cf0c11f1a893c189592c5115&vids=1&msclkid=N&pi=918639831&lg.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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