pesca.restaurant website review

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

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

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

8 third-party services load with your homepage (formitable.com, Google Tag Manager and qooqie.com and others), adding 4.9 MB and 855 ms of main-thread time.

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

11 images could be 859 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

formitable.com costs a phone 332 ms of main-thread work and 541 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.

Azure Web Services costs a phone 0 ms of main-thread work and 3.7 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.

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

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

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

Desktop scores 80 but mobile only 53. 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.

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.53 (75th percentile). Good is under 0.1.

Your largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

Your homepage downloads 6.8 MB in 101 requests on a phone: images 5.2 MB (20), scripts 1.3 MB (49) and fonts 162 KiB (8). Under 2 MB keeps phones on slow connections fast.

2 images (92 KiB) 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.

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

1 button has no accessible name, so screen readers announce just “button”.

2 frames have no title, so screen-reader users cannot tell what they contain.

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

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

ARIA role should be appropriate for the element: 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.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 36 pages on pesca.restaurant and 6 external pages.

There is no https://pesca.restaurant/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.

https://pesca.restaurant/fr and https://pesca.restaurant/de all use the title “Home - Pesca”. Search engines can't tell which page to show for a search, so each competes with the others.

https://pesca.restaurant/locations, https://pesca.restaurant/about, https://pesca.restaurant/faq, https://pesca.restaurant/blogs, https://pesca.restaurant/fr and https://pesca.restaurant/de and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://pesca.restaurant/blogs has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “GA4 is not defined or Measurement ID is missing”.

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

Chrome logged issues while loading the page (“Cookie”).

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

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

The homepage carries about 648 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 3 cookies, 1 of them by other companies (measured from a US location before any click).

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