Website review, no card needed

rubiomonocoat.it logo

rubiomonocoat.it website review

Visit site (opens in a new tab)Reviewed 7 November 202642 issues · 86 checks

This review found 42 issues worth fixing on rubiomonocoat.it, 15 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.1 s2.5 sSep 5Oct 313.1 s
Show as table
DateReal-visitor load time (LCP)
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20262.9 s
Oct 10, 20262.6 s
Oct 17, 20262.7 s
Oct 24, 20262.8 s
Oct 31, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
252 ms197 msSep 5Oct 31216 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 2026229 ms
Sep 12, 2026246 ms
Sep 19, 2026234 ms
Sep 26, 2026245 ms
Oct 3, 2026237 ms
Oct 10, 2026203 ms
Oct 17, 2026206 ms
Oct 24, 2026204 ms
Oct 31, 2026216 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

Full-page screenshot of rubiomonocoat.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rubiomonocoat.it at 0.4 s0.4 s
  2. rubiomonocoat.it at 0.8 s0.8 s
  3. rubiomonocoat.it at 1.2 s1.2 s
  4. rubiomonocoat.it at 1.6 s1.6 s
  5. rubiomonocoat.it at 2.0 s2.0 s
  6. rubiomonocoat.it at 2.4 s2.4 s
  7. rubiomonocoat.it at 2.8 s2.8 s
  8. rubiomonocoat.it at 3.2 s3.2 s

Speed

11 to fix58
  • Render-blocking requests

    2.2 s

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

  • Main-thread work: 4.9 s

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

  • Improve image delivery

    2.0 MB

    28 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    300 ms · 701 KiB

    About 701 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.

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (rebuyengine.com, Shopify and Klaviyo and others), adding 1.4 MB and 658 ms of main-thread time.

  • Reduce unused CSS

    600 ms · 117 KiB

    About 117 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Use efficient cache lifetimes

    450 ms · 201 KiB

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

  • 2,429 HTML elements

    The page has 2,429 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • rebuyengine.com adds 169 ms

    169 ms

    rebuyengine.com costs a phone 169 ms of main-thread work and 679 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 135 ms

    135 ms

    Klaviyo costs a phone 135 ms of main-thread work and 331 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.

  • 5 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    62 KiB

    Polyfills for old browsers add 62 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 CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 16 ms

    16 ms

    Your server sent the HTML in 16 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix0
  • 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: 26.2 s

    26.2 s

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

  • Largest Contentful Paint: 7.3 s

    7.3 s

    Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user INP: 222 ms

    222 ms

    Real visitors wait 222 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.11

    0.11

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

  • Real-user FCP: 2.0 s

    2.0 s

    Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 877 ms

    877 ms

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

  • Total Blocking Time: 247 ms

    247 ms

    Scripts block taps and scrolling for 247 ms in total while the page loads. Good is under 200 ms.

  • Largest content (LCP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Tap response (INP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 229 ms to 216 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.003

    0.003

    The layout barely moves while loading (CLS 0.003, good is under 0.1).

Images and page weight

3 to fix50
  • Page weight: 18.0 MB in 358 requests

    18.0 MB

    Your homepage downloads 18.0 MB in 358 requests on a phone: media 12.1 MB (4), images 2.8 MB (77) and scripts 1.3 MB (102). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (660 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 far larger than shown

    109 KiB

    2 images are downloaded at several times the size a phone draws them, for example Cleaner_1L.webp at 390 px wide, shown at 40 px. Resized copies would save about 109 KiB.

  • 3 images below the first screen load straight away

    3 images further down the page (164 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 5.1 g of CO₂ per visit

    5.11 g

    By the Sustainable Web Design model, a visit to your homepage emits about 5.11 g of CO₂e: 613.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

6 to fixGoogle 8790
  • 9 buttons without a name

    9 buttons have no accessible name, so screen readers announce just “button”.

  • 23 text elements with low contrast

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

  • 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.

  • 34 images without alt text

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

  • 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9283
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “Rubio Monocoat - Olio per legno ad alte prestazioni per interno ed esterno”.

  • 143 internal links, 3 external

    The homepage links to 143 pages on rubiomonocoat.it and 3 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Protezione durevole del legno con una sola mano. Finitura naturale per pavimenti, mobili e superfici esterne. Ordina ra…”.

  • Canonical URL set

    The canonical URL is https://rubiomonocoat.it/.

  • 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://rubiomonocoat.it/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://rubiomonocoat.it/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (903 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 5 pages without an H1

    https://rubiomonocoat.it/pages/all-reviews-page, https://rubiomonocoat.it/pages/servizio-clienti, https://rubiomonocoat.it/collections/preparazione-legno-interni, https://rubiomonocoat.it/collections/pretrattamento-legno-interni and https://rubiomonocoat.it/collections/olio-legno-interni have 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 61 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    5 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.

  • Every page has a meta description

    All 5 pages that loaded have a meta description.

  • 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 5 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://rubiomonocoat.it/.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    20 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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.

  • 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.

  • 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.

  • 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 622 words of copy

    The homepage carries about 622 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Order colour samples”.

  • 11 short forms

    11 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads 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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 37 other companies contacted

    Loading the homepage contacts 37 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 rubiomonocoat.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Magento;Shopify;Shopify Plus
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on rubiomonocoat.it, including 22 speed issues, 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25