Website review, no card needed
ricomoda.com website review
Visit site (opens in a new tab)Reviewed 16 November 202633 issues · 83 checks
This review found 33 issues worth fixing on ricomoda.com, 10 of them high impact, across 83 checks. The most urgent: improve image delivery. 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
80B- #46,139 of 117,151 reviewed websitesbeats 55%
- #30,841 of 66,872 online storesbeats 47%
- #29,677 of 60,987 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
| Nov 7, 2026 | 1.1 s |
| Nov 14, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 107 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 110 ms |
| Jul 25, 2026 | 109 ms |
| Aug 1, 2026 | 110 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 108 ms |
| Aug 29, 2026 | 107 ms |
| Sep 5, 2026 | 107 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 109 ms |
| Sep 26, 2026 | 109 ms |
| Oct 3, 2026 | 105 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 103 ms |
| Oct 24, 2026 | 102 ms |
| Oct 31, 2026 | 104 ms |
| Nov 7, 2026 | 107 ms |
| Nov 14, 2026 | 112 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
Speed
Improve image delivery
2.6 s · 915 KiB8 images could be 915 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Main-thread work: 13.4 s
A phone's processor spends 13.4 s on main-thread work while loading, 4.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Facebook and Klaviyo and others), adding 1.8 MB and 1.4 s of main-thread time.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
523 KiBAbout 523 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
500 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Shopify adds 348 ms
348 msShopify costs a phone 348 ms of main-thread work and 598 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 380 ms. During a long task the page ignores taps.
Facebook adds 327 ms
327 msFacebook costs a phone 327 ms of main-thread work and 253 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.
Klaviyo adds 270 ms
270 msKlaviyo costs a phone 270 ms of main-thread work and 330 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.
Use efficient cache lifetimes
300 KiB10 files are served with short cache lifetimes, so returning visitors download them again (300 KiB).
2,256 HTML elements
The page has 2,256 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
LoyaltyLion adds 129 ms
129 msLoyaltyLion costs a phone 129 ms of main-thread work and 360 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.
Legacy JavaScript
66 KiBPolyfills for old browsers add 66 KiB JavaScript that modern phones do not need.
Reduce unused CSS
50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page.
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 23.7 s
23.7 sThe page becomes fully interactive after 23.7 s. Good is under 3.8 s.
Speed Index: 12.9 s
12.9 sVisually, the page fills in at 12.9 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 7.5 s
7.5 sYour largest element takes 7.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: 572 ms
572 msScripts block taps and scrolling for 572 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 105 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 561 ms
561 msReal visitors wait 561 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 6.1 MB in 502 requests
6.1 MBYour homepage downloads 6.1 MB in 502 requests on a phone: images 2.5 MB (114), scripts 2.3 MB (215) and other files 816 KiB (131). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (393 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.
About 1.7 g of CO₂ per visit
1.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.74 g of CO₂e: 208.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 95 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 2 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.
235 internal links, 5 external
The homepage links to 235 pages on ricomoda.com and 5 external pages.
7 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “Vind jouw exclusieve designerkleding van merken als Stone Island, Parajumpers, Flaneur, CP Company en meer voor mannen …”.
Title: 55 characters
Your title is a healthy 55 characters: “Rico Moda | De exclusieve multi-brand store voor mannen”.
Canonical URL set
The canonical URL is https://ricomoda.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://ricomoda.com/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, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (690 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ricomoda.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://ricomoda.com/collections/nieuw is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://ricomoda.com/collections/barmas has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://ricomoda.com/pages/alle-merken has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 101 found) and read each the way a search engine does.
4 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
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 a title
All 11 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5035492&tm=gtm002&Ver=2&mid=6c00c6e6-6e3e-4b96-9d59-f0ae88f72e41&bo=1&sid=81098420e1d511f1a1313f37fc3aba6c&vid=8109b260e1d511f1833a574c8e000ed5&vids=1&msclkid=N&pi=918.
15 small tap targets
15 of 68 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 23 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 499 words of copy
The homepage carries about 499 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Klaviyo, Meta Pixel and Microsoft Ads and 1 more (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.
21 cookies set on arrival
21Opening the homepage sets 21 cookies (measured from a US location before any click).
No consent tool detected
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.
35 other companies contacted
Loading the homepage contacts 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 ricomoda.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on ricomoda.com, including 17 speed issues, 1 SEO issue 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.