Website review, no card needed

mesaudanailpro.it logo

mesaudanailpro.it website review

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

This review found 42 issues worth fixing on mesaudanailpro.it, 13 of them high impact, across 86 checks. The most urgent: iubenda adds 1.6 s. 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.1 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.4 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.3 s
Oct 10, 20261.4 s
Oct 17, 20261.6 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
284 ms145 msMay 16Oct 31165 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026213 ms
May 23, 2026204 ms
May 30, 2026205 ms
Jun 6, 2026204 ms
Jun 13, 2026206 ms
Jun 20, 2026214 ms
Jun 27, 2026220 ms
Jul 4, 2026227 ms
Jul 11, 2026229 ms
Jul 18, 2026235 ms
Jul 25, 2026240 ms
Aug 1, 2026247 ms
Aug 8, 2026260 ms
Aug 15, 2026261 ms
Aug 22, 2026268 ms
Aug 29, 2026264 ms
Sep 5, 2026263 ms
Sep 12, 2026261 ms
Sep 19, 2026248 ms
Sep 26, 2026231 ms
Oct 3, 2026201 ms
Oct 10, 2026183 ms
Oct 17, 2026168 ms
Oct 24, 2026161 ms
Oct 31, 2026165 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 mesaudanailpro.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mesaudanailpro.it at 0.5 s0.5 s
  2. mesaudanailpro.it at 1.0 s1.0 s
  3. mesaudanailpro.it at 1.4 s1.4 s
  4. mesaudanailpro.it at 1.9 s1.9 s
  5. mesaudanailpro.it at 2.4 s2.4 s
  6. mesaudanailpro.it at 2.9 s2.9 s
  7. mesaudanailpro.it at 3.4 s3.4 s
  8. mesaudanailpro.it at 3.8 s3.8 s

Speed

14 to fix54
  • iubenda adds 1.6 s

    1.6 s

    iubenda costs a phone 1.6 s of main-thread work and 126 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.

  • Main-thread work: 10.8 s

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

  • Render-blocking requests

    1.1 s

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

  • 5,015 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (iubenda, Amazon Web Services and Shopify and others), adding 1.9 MB and 3.3 s of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • Amazon Web Services adds 890 ms

    890 ms

    Amazon Web Services costs a phone 890 ms of main-thread work and 36 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

    400 ms · 489 KiB

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

  • Reduce unused JavaScript

    666 KiB

    About 666 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    507 KiB

    11 images could be 507 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    450 ms

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

  • 20 long tasks on the main thread

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

  • Shopify adds 210 ms

    210 ms

    Shopify costs a phone 210 ms of main-thread work and 587 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 167 ms

    167 ms

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

  • Reduce unused CSS

    150 ms · 29 KiB

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

  • Minify JavaScript

    150 ms · 13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    53 KiB

    Polyfills for old browsers add 53 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    15 KiB

    15 KiB JavaScript is shipped twice across bundles.

  • 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: 48 ms

    48 ms

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

Core Web Vitals

9 to fix67
  • 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: 20.1 s

    20.1 s

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

  • Total Blocking Time: 1.5 s

    1.5 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • Real-user INP: 293 ms

    293 ms

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

  • Largest content (LCP) got 43% slower for real visitors

    +43%

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

  • Largest Contentful Paint: 3.8 s

    3.8 s

    Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Carica video: NEW TOP COAT”.

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 3 images without width and height

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

6 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

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

    1.7 s

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

  • Real-user TTFB: 731 ms

    731 ms

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

  • Tap response (INP) got 22% faster for real visitors

    -22%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix64
  • Page weight: 4.4 MB in 385 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 385 requests on a phone: scripts 2.1 MB (134), other files 1.1 MB (183) and images 960 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    dc62699317964976b5cbe95785b90715.thumbnail.0000000000.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (104 KiB) is 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.3 g of CO₂ per visit

    1.26 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 151.3 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 9694
  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • 10 images without alt text

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

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

  • 19 links without text

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

  • Headings should not be empty (8 elements)

    Headings should not be empty: 8 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 55 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 4 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 9290
  • Meta description is long (161 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 205 internal links, 16 external

    The homepage links to 205 pages on mesaudanailpro.it and 16 external pages.

6 checks passed
  • Title: 46 characters

    Your title is a healthy 46 characters: “MyNailPro | Il mio professionista delle unghie”.

  • Canonical URL set

    The canonical URL is https://www.mynailpro.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://www.mynailpro.com/sitemap.xml.

AI search readiness

100
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 (1,658 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.mynailpro.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 5 pages without a meta description

    https://www.mynailpro.com/pages/chi-inizia, https://www.mynailpro.com/pages/my-wishlist, https://www.mynailpro.com/collections/preparatori, https://www.mynailpro.com/collections/basi and https://www.mynailpro.com/collections/top-coat have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.mynailpro.com/collections/universal-rubber-base and https://www.mynailpro.com/products/rubber-base-103-macrame use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.mynailpro.com/collections/genie-in-a-bottle%E2%84%A2, whose canonical is https://www.mynailpro.com/collections/genie-in-a-bottle%e2%84%a2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 80 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

Best practices

3 to fixGoogle 9285
  • 19 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute width: Expected length, "large".”.

  • 1 distorted image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 5 customer or partner logos. 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 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 923 words of copy

    The homepage carries about 923 words of visible text.

  • Urgency cues

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

2 checks passed
  • 35 short forms

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

  • Direct contact links

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

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Meta Pixel (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies (measured from a US location before any click).

  • 34 other companies contacted

    Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) 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 mesaudanailpro.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 21 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Yotpo Loyalty Rewards · Wsh Wholesale Pricing · Klaviyo Email Marketing Sms · Sami Wholesale · Motive Privacy Minded Search · Pagefly Ai Page Builder · Hulk Form Builder · Cmp Insert Code · Yotpo Product Reviews · Eg Auto Add To Cart · Shopify App Template Php · Forms · Store Locator · Prod Master Fad8e300 · Theme App Extension Prod · Wishlist Power · amazonaws.com · orichi.info · getsitecontrol.com · cloudfront.net · roseperl.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

Framework
Tailwind CSS
E-commerce
Shopify
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 mesaudanailpro.it, including 23 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