Website review, no card needed
rocskincare.it website review
Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 79 checks
This review found 33 issues worth fixing on rocskincare.it, 11 of them high impact, across 79 checks. The most urgent: page weight: 14.7 MB in 214 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
70C- #104,629 of 125,753 reviewed websitesbeats 14%
- #63,056 of 70,254 online storesbeats 8%
- #58,264 of 63,820 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 155 ms |
| May 30, 2026 | 155 ms |
| Jun 6, 2026 | 162 ms |
| Jun 13, 2026 | 166 ms |
| Jun 20, 2026 | 166 ms |
| Jun 27, 2026 | 168 ms |
| Jul 4, 2026 | 170 ms |
| Jul 11, 2026 | 171 ms |
| Jul 18, 2026 | 178 ms |
| Jul 25, 2026 | 180 ms |
| Aug 1, 2026 | 171 ms |
| Aug 8, 2026 | 171 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 157 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 140 ms |
| Sep 26, 2026 | 147 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 167 ms |
| Oct 24, 2026 | 173 ms |
| Oct 31, 2026 | 174 ms |
| Nov 7, 2026 | 174 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
Mobile performance score: 49
49/100Your mobile performance score is 49. 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, Facebook and roseperl.com and others), adding 11.3 MB and 1.4 s of main-thread time.
Shopify adds 53 ms
53 msShopify costs a phone 53 ms of main-thread work and 9.7 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.
Use efficient cache lifetimes
770 KiB22 files are served with short cache lifetimes, so returning visitors download them again (770 KiB).
Reduce unused JavaScript
200 ms · 445 KiBAbout 445 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 200 ms faster on a phone.
Google Tag Manager adds 502 ms
502 msGoogle Tag Manager costs a phone 502 ms of main-thread work and 509 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.
Facebook adds 379 ms
379 msFacebook costs a phone 379 ms of main-thread work and 341 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.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
roseperl.com adds 253 ms
253 msroseperl.com costs a phone 253 ms of main-thread work and 482 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,784 HTML elements
The page has 2,784 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 256 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Reduce unused CSS
51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
Improve image delivery
6 KiB1 image could be 6 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 12 ms
12 msYour server sent the HTML in 12 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: 18.8 s
18.8 sThe page becomes fully interactive after 18.8 s. Good is under 3.8 s.
First Contentful Paint: 4.8 s
4.8 sThe first text or image appears after 4.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 4.8 s
4.8 sYour largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Noi e i nostri partner, incluso Shopify, utilizziamo cookie…”. Most of its time is element render delay (2.5 s).
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 738 ms
738 msScripts block taps and scrolling for 738 ms in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.21
0.21For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 155 ms to 174 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
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: 180 ms
180 msReal visitors wait 180 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Images and page weight
Page weight: 14.7 MB in 214 requests
14.7 MBYour homepage downloads 14.7 MB in 214 requests on a phone: media 11.2 MB (2), scripts 1.9 MB (51) and images 812 KiB (61). Under 2 MB keeps phones on slow connections fast.
About 4.2 g of CO₂ per visit
4.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.16 g of CO₂e: 499.8 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
19 form fields without a label
19 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 65 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “RoC Skincare Italia | Retinolo e Trattamenti Anti-Età – RoC Italia”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“RoC Italia” and “RoC Italia”). One clear main headline is easier for people and search engines.
213 internal links, 2 external
The homepage links to 213 pages on rocskincare.it and 2 external pages.
5 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Scopri RoC Skincare Italia: trattamenti viso anti-età clinicamente provato con retinolo, acido ialuronico e altri attiv…”.
Canonical URL set
The canonical URL is https://rocskincare.it/.
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://rocskincare.it/sitemap.xml.
AI search readiness
No Organization structured data
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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (897 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://rocskincare.it/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://rocskincare.it/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://rocskincare.it/collections/shop-all took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 56 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 15 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
44 of 45 tappable elements near the top are at least 24 px.
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 264 words of copy
The homepage carries about 264 words of visible text.
2 checks passed
20 short forms
20 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Plausible.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 1 of them by other companies (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.
22 other companies contacted
Loading the homepage contacts 22 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 rocskincare.it, 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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
roseperl.com · bazaarvoice.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 | Plausible
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on rocskincare.it, including 18 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.