Website review, no card needed
modibodi.co.uk website review
Visit site (opens in a new tab)Reviewed 5 November 202645 issues · 98 checks
This review found 45 issues worth fixing on modibodi.co.uk, 16 of them high impact, across 98 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73C- #90,725 of 122,703 reviewed websitesbeats 23%
- #56,685 of 69,252 online storesbeats 15%
- #53,073 of 63,070 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 128 ms |
| May 23, 2026 | 124 ms |
| May 30, 2026 | 124 ms |
| Jun 6, 2026 | 126 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 133 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 140 ms |
| Jul 18, 2026 | 139 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 134 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 122 ms |
| Sep 12, 2026 | 120 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 122 ms |
| Oct 24, 2026 | 123 ms |
| Oct 31, 2026 | 123 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.3 s
3.4 s
4.6 s
5.7 s
6.9 s
8.0 s
9.2 s
Speed
Render-blocking requests
1.3 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Main-thread work: 10.4 s
A phone's processor spends 10.4 s on main-thread work while loading, 6.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, rebuyengine.com and Clarity and others), adding 2.6 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
360 ms · 869 KiBAbout 869 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 360 ms faster on a phone.
Improve image delivery
671 KiB11 images could be 671 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
150 ms · 501 KiB42 files are served with short cache lifetimes, so returning visitors download them again (501 KiB).
Google Tag Manager adds 447 ms
447 msGoogle Tag Manager costs a phone 447 ms of main-thread work and 526 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.
Reduce unused CSS
300 ms · 124 KiBAbout 124 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.
rebuyengine.com adds 280 ms
280 msrebuyengine.com costs a phone 280 ms of main-thread work and 914 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.
2,373 HTML elements
The page has 2,373 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
OptiMonk adds 178 ms
178 msOptiMonk costs a phone 178 ms of main-thread work and 469 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.
Optanon adds 150 ms
150 msOptanon costs a phone 150 ms of main-thread work and 424 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 209 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 30 KiB30 KiB could be saved by minifying JavaScript.
Legacy JavaScript
104 KiBPolyfills for old browsers add 104 KiB JavaScript that modern phones do not need.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Duplicated JavaScript
40 KiB40 KiB JavaScript is shipped twice across bundles.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Time to Interactive: 33.8 s
33.8 sThe page becomes fully interactive after 33.8 s. Good is under 3.8 s.
Speed Index: 13.6 s
13.6 sVisually, the page fills in at 13.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.23
0.23For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 128 ms to 123 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 395 ms
395 msReal visitors wait 395 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 447 requests
6.3 MBYour homepage downloads 6.3 MB in 447 requests on a phone: scripts 2.6 MB (151), images 1.6 MB (42) and other files 1.3 MB (210). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
LEOPARD-HERO-MOBILE-V001_b199fb7a-6324-4c21-8c2d-64817431cef is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
6 images far larger than shown
265 KiB6 images are downloaded at several times the size a phone draws them, for example FEAT-AUG26-BTS-001.jpg at 624 px wide, shown at 193 px. Resized copies would save about 265 KiB.
2 images in older formats
2 images (384 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.
2 images below the first screen load straight away
2 images further down the page (156 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.79 g of CO₂e: 215.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Required ARIA attributes must be provided (8 elements)
Required ARIA attributes must be provided: 8 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Unlabelled dropdowns
1 dropdown has no label.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (1 element).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
252 internal links, 12 external
The homepage links to 252 pages on modibodi.co.uk and 12 external pages.
6 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “With various designs of leak proof underwear available, Modibodi is your one-stop shop for stylish feminine hygiene und…”.
Title: 62 characters
Your title is a healthy 62 characters: “The Original Period Pants & Leak Proof Underwear | Modibodi UK”.
Canonical URL set
The canonical URL is https://www.modibodi.co.uk/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.modibodi.co.uk/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and description; logo and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,316 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.modibodi.co.uk/llms.txt (7 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://www.modibodi.co.uk/collections/back-in-stock, https://www.modibodi.co.uk/collections/all and https://www.modibodi.co.uk/collections/limited-edition have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 79 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
15 small tap targets
15 of 47 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “None is not defined”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,180 words of copy
The homepage carries about 1,180 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “STOCK UP AND SAVE - SHOP VALUE PACKS” and “Shop”.
33 calls to action
The homepage has 33 calls to action, for example “STOCK UP AND SAVE - SHOP VALUE PACKS”, “Shop” and “Shop All”.
4 short forms
4 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
34 cookies set on arrival
34Opening the homepage sets 34 cookies (measured from a US location before any click).
80 other companies contacted
Loading the homepage contacts 80 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at modibodi.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 19 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geo Pro Geolocation · Okendo · Nosto · Analyzify Ga4 Ads Tracking · Microsoft Clarity · Hreflang Tags · Tolstoy · Optimonk Popup Cro A B Test · Gorgias Live Chat Helpdesk · Triplewhale · Easylocation · Loop Returns · privy.com · snapchat.com · emarsys.net · scarabresearch.com · rakutenadvertising.io · rebuyengine.com · 9gtb.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on modibodi.co.uk, including 20 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.