Website review, no card needed
roccamore.se website review
Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 91 checks
This review found 43 issues worth fixing on roccamore.se, 14 of them high impact, across 91 checks. The most urgent: main-thread work: 16.0 s. 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- #87,310 of 117,615 reviewed websitesbeats 22%
- #54,889 of 66,923 online storesbeats 15%
- #51,445 of 61,018 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Main-thread work: 16.0 s
A phone's processor spends 16.0 s on main-thread work while loading, 10.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.4 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Google Tag Manager adds 1.3 s
1.3 sGoogle Tag Manager costs a phone 1.3 s of main-thread work and 889 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 48
48/100Your mobile performance score is 48. 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, roccamore.no and Klaviyo and others), adding 2.2 MB and 3.4 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.6 s. During a long task the page ignores taps.
Reduce unused JavaScript
854 KiBAbout 854 KiB of JavaScript is downloaded but never used on this page.
roccamore.no adds 651 ms
651 msroccamore.no costs a phone 651 ms of main-thread work and 284 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 582 ms
582 msKlaviyo costs a phone 582 ms of main-thread work and 320 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.
TikTok adds 250 ms
250 msTikTok costs a phone 250 ms of main-thread work and 156 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,469 HTML elements
The page has 2,469 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
LoyaltyLion adds 188 ms
188 msLoyaltyLion costs a phone 188 ms of main-thread work and 356 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
112 KiB14 files are served with short cache lifetimes, so returning visitors download them again (112 KiB).
Improve image delivery
52 KiB4 images could be 52 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
43 KiBAbout 43 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need.
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
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 33 ms
33 msYour server sent the HTML in 33 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 17.3 s
17.3 sVisually, the page fills in at 17.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 4.9 s
4.9 sScripts block taps and scrolling for 4.9 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 31.0 s
31.0 sThe page becomes fully interactive after 31.0 s. Good is under 3.8 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.7 s
2.7 sYour largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THE WORLD WASN'T DESIGNED AROUND WOMEN. WE MAKE PRODUCTS TH…”. Most of its time is element render delay (1.6 s).
Cumulative Layout Shift: 0.117
0.117The layout shifts by 0.117 while loading, so content jumps under the reader's thumb. Good is under 0.1.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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.
Images and page weight
Page weight: 5.3 MB in 275 requests
5.3 MBYour homepage downloads 5.3 MB in 275 requests on a phone: scripts 2.5 MB (130), images 1.9 MB (26) and other files 685 KiB (91). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
2026_Virginia_Large_Pebbled_Black_packshoot_278d3f8b-84c3-40 weighs 672 KiB. On a phone connection a single image that size takes seconds.
About 1.5 g of CO₂ per visit
1.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.49 g of CO₂e: 178.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
115 text elements with low contrast
115 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
86 tap targets too small
86 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
163 images without alt text
163 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (110 elements)
All page content should be contained by landmarks: 110 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (9 elements)
Headings should not be empty: 9 elements on the page fail this check, rated minor by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
44 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: 44 passed and 12 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“SCIENTIFICALLY VALIDATED COMFORT”, “” and “ROCCAMORE IN THE PRESS”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
267 internal links, 8 external
The homepage links to 267 pages on roccamore.se and 8 external pages.
6 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Roccamore are comfortable handmade shoes and boots. The scientifically validated insole gives you more comfort. Approve…”.
Title: 54 characters
Your title is a healthy 54 characters: “Roccamore - comfortable high heels. Handmade in Italy.”.
Canonical URL set
The canonical URL is https://roccamore.se/.
Structured data in place
Structured data found: Organization and WebSite.
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://roccamore.se/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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (447 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://roccamore.se/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://roccamore.se/collections/new-arrivals, https://roccamore.se/pages/bags, https://roccamore.se/collections/accessories, https://roccamore.se/collections/loafers, https://roccamore.se/collections/sandals and https://roccamore.se/collections/virginia-collection have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://roccamore.se/collections/new-arrivals, https://roccamore.se/collections/last-chance-to-buy, https://roccamore.se/collections/icon, https://roccamore.se/collections/roccamore-boots, https://roccamore.se/collections/pumps and https://roccamore.se/collections/loafers and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages slow to respond
https://roccamore.se/products/gift-card, https://roccamore.se/pages/bags, https://roccamore.se/pages/roccamore-wedding-salon, https://roccamore.se/collections/accessories, https://roccamore.se/collections/roccamore-boots and https://roccamore.se/collections/pumps and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 79 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://roccamore.se/.
293 small tap targets
293 of 351 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “lion is not defined”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 50 testimonial or review blocks. 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 434 words of copy
The homepage carries about 434 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP ALL”.
3 calls to action
The homepage has 3 calls to action, for example “SHOP” and “SHOP ALL”.
Analytics in place
Analytics detected: Google Tag Manager and TikTok Pixel.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Klaviyo, LinkedIn Insight and Meta Pixel (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.
11 cookies set on arrival
11Opening the homepage sets 11 cookies (measured from a US location before any click).
33 other companies contacted
Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 roccamore.se, 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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Okendo · Loyalty Rewards And Referrals · Klaviyo Email Marketing Sms · Stape Remix · gorgias.chat · 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
- The footer still says © 2022.
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on roccamore.se, including 19 speed issues, 2 SEO issues and 2 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.