Website review, no card needed

robertoverino.com logo

robertoverino.com website review

Visit site (opens in a new tab)Reviewed 18 November 202641 issues · 83 checks

This review found 41 issues worth fixing on robertoverino.com, 9 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.

  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
1.8 s1.5 sMay 30Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.7 s
Nov 7, 20261.7 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
133 ms96 msMay 30Nov 14104 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026100 ms
Jun 6, 2026106 ms
Jun 13, 2026112 ms
Jun 20, 2026119 ms
Jun 27, 2026121 ms
Jul 4, 2026122 ms
Jul 11, 2026122 ms
Jul 18, 2026121 ms
Jul 25, 2026121 ms
Aug 1, 2026121 ms
Aug 8, 2026124 ms
Aug 15, 2026127 ms
Aug 22, 2026129 ms
Aug 29, 2026129 ms
Sep 5, 2026128 ms
Sep 12, 2026127 ms
Sep 19, 2026128 ms
Sep 26, 2026128 ms
Oct 3, 2026127 ms
Oct 10, 2026123 ms
Oct 17, 2026115 ms
Oct 24, 2026110 ms
Oct 31, 2026105 ms
Nov 7, 2026104 ms
Nov 14, 2026104 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 robertoverino.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. robertoverino.com at 0.4 s0.4 s
  2. robertoverino.com at 0.8 s0.8 s
  3. robertoverino.com at 1.1 s1.1 s
  4. robertoverino.com at 1.5 s1.5 s
  5. robertoverino.com at 1.9 s1.9 s
  6. robertoverino.com at 2.3 s2.3 s
  7. robertoverino.com at 2.6 s2.6 s
  8. robertoverino.com at 3.0 s3.0 s

Speed

11 to fix30
  • Improve image delivery

    1.8 s · 392 KiB

    6 images could be 392 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

  • Mobile performance score: 30

    30/100

    Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused JavaScript

    450 ms · 916 KiB

    About 916 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 7 third-party services on the page

    7 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 1.5 MB and 922 ms of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 296 KiB

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

  • Reduce unused CSS

    600 ms · 233 KiB

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

  • Render-blocking requests

    800 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 800 ms.

  • YouTube adds 524 ms

    524 ms

    YouTube costs a phone 524 ms of main-thread work and 1,018 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.

  • Font display

    600 ms

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

  • Google Tag Manager adds 329 ms

    329 ms

    Google Tag Manager costs a phone 329 ms of main-thread work and 342 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: 2.2 s

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

1 checks passed
  • Server response: 114 ms

    114 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 9.4 s

    9.4 s

    Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “OI2026 - Home - 17 Noviembre - 20261117 - 3 (mobile)”.

  • Cumulative Layout Shift: 0.908

    0.908

    The layout shifts by 0.908 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 17.6 s

    17.6 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Real-user TTFB: 836 ms

    836 ms

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

  • Total Blocking Time: 532 ms

    532 ms

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

  • 6 images without width and height

    6 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 113 ms

    113 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

Images and page weight

3 to fix68
  • Page weight: 3.8 MB in 50 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 50 requests on a phone: images 1.7 MB (17), scripts 1.7 MB (13) and stylesheets 191 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 11 images below the first screen load straight away

    11 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 4 images in older formats

    4 images (699 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.1 g of CO₂ per visit

    1.08 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8392
  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

  • 13 images without alt text

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

6 to fixGoogle 8574
  • Title is short (29 characters)

    Your title is only 29 characters: “Online Store - Roberto Verino”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “TONIGHT, MAYBE” and “TONIGHT, MAYBE”). One clear main headline is easier for people and search engines.

  • Meta description is long (163 characters)

    Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 124 internal links, 7 external

    The homepage links to 124 pages on robertoverino.com and 7 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.robertoverino.com/en/.

  • 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.robertoverino.com/index_sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.robertoverino.com/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.

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

Other pages

2 to fix88
  • 2 pages share a title

    / and https://www.robertoverino.com/en all use the title “Online Store - Roberto Verino”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.robertoverino.com/en/20261884-tonight-maybe has 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 72 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.

  • 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

2 to fixGoogle 9287
  • 17 small tap targets

    17 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 134 words

    The homepage has only about 134 words of visible text; thin pages give Google and first-time buyers little to go on.

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP BAGS”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “SHOP WOMAN”, “SHOP MAN” and “SHOP BAGS”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.

  • 9 cookies set on arrival

    9

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

  • 12 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics | Microsoft Clarity
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on robertoverino.com, including 19 speed issues, 6 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

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