mrsool.co website review

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

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

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

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

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

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

2 third-party services load with your homepage (JSDelivr CDN and Unpkg), adding 67 KiB and 79 ms of main-thread time.

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

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

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

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

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.

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

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

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mrsool helps you, Send things t|”. Most of its time is element render delay (2.9 s).

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 122 ms to 138 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 3.5 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 25.8 MB in 97 requests on a phone: media 25.0 MB (4), scripts 385 KiB (36) and images 273 KiB (15). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (21 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 7.32 g of CO₂e: 878.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

7 images have no alt text, which hurts accessibility and image search.

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

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 28 characters: “MRSOOL | We Say It, We Do It”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 32 pages on mrsool.co and 16 external pages.

Your homepage links to https://mrsool.co/shops/aac2f611ca6801088cbdf9714efa2857, https://mrsool.co/shops/0486c948845c186a60d292e4a5ceef5e, https://mrsool.co/shops/d51a6474bff9265536de97190391aa0f, https://mrsool.co/shops/e06cc0df66b74e3305b8ca46737e9003, https://mrsool.co/shops/d79648138eaeb6de24a5c37021a567c5 and https://mrsool.co/shops/4f30dc580e962baf2f4bd26e32088242 and 1 other, which answer with an error. Visitors hit a dead end and search engines drop them.

https://mrsool.co/home and / all use the title “MRSOOL | We Say It, We Do It”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://mrsool.co/home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mrsool.co/about, https://mrsool.co/couriers and https://mrsool.co/partnership have no <h1> headline, so visitors and search engines get no clear main topic.

https://mrsool.co/couriers and https://mrsool.co/get-in-touch have 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 12 pages linked from your homepage and read each the way a search engine does.

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

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

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

Your homepage shows a street address 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.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Opening the homepage sets 1 cookie (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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.