pocketresult.com website review

8 third-party services load with your homepage (Google Tag Manager, weglot.com and dorik.com and others), adding 8.8 MB and 338 ms of main-thread time.

dorik.com costs a phone 51 ms of main-thread work and 8.1 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.

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

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

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

About 353 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 180 ms faster on a phone.

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

dorik.io costs a phone 3 ms of main-thread work and 307 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.

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

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

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.

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

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

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

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

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 8.9 MB in 39 requests on a phone: media 7.2 MB (2), images 1.1 MB (18) and scripts 521 KiB (11). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 1200px-Logo_SNCF_Reseau_2015.svg_-1080x762_343uqmkg.png at 799 px wide, shown at 40 px. Resized copies would save about 107 KiB.

1 image (31 KiB) is 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 2.51 g of CO₂e: 301.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

All page content should be contained by landmarks: 63 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

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

The homepage links to 55 pages on pocketresult.com and 3 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://pocketresult.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.

https://pocketresult.com/Certifications-environnementales has no <title>, so Google invents the link text in results.

https://pocketresult.com/Certifications-environnementales, https://pocketresult.com/gestion-des-processus and https://pocketresult.com/gestion-des-tiers have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

5 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

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

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

The homepage shows no opening hours. If customers visit or call, show when.

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

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