Website review, no card needed
pomellato.com website review
Visit site (opens in a new tab)Reviewed 1 November 202645 issues · 93 checks
This review found 45 issues worth fixing on pomellato.com, 20 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.2 s |
| May 16, 2026 | 4.1 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 331 ms |
| May 16, 2026 | 331 ms |
| May 23, 2026 | 328 ms |
| May 30, 2026 | 322 ms |
| Jun 6, 2026 | 332 ms |
| Jun 13, 2026 | 337 ms |
| Jun 20, 2026 | 345 ms |
| Jun 27, 2026 | 352 ms |
| Jul 4, 2026 | 351 ms |
| Jul 11, 2026 | 349 ms |
| Jul 18, 2026 | 342 ms |
| Jul 25, 2026 | 334 ms |
| Aug 1, 2026 | 331 ms |
| Aug 8, 2026 | 331 ms |
| Aug 15, 2026 | 334 ms |
| Aug 22, 2026 | 339 ms |
| Aug 29, 2026 | 349 ms |
| Sep 5, 2026 | 356 ms |
| Sep 12, 2026 | 359 ms |
| Sep 19, 2026 | 357 ms |
| Sep 26, 2026 | 352 ms |
| Oct 3, 2026 | 342 ms |
| Oct 10, 2026 | 328 ms |
| Oct 17, 2026 | 327 ms |
| Oct 24, 2026 | 329 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
How it loaded on a phone
1.1 s
2.1 s
3.2 s
4.3 s
5.4 s
6.4 s
7.5 s
8.6 s
Speed
Reduce unused JavaScript
5.8 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.
Main-thread work: 11.1 s
A phone's processor spends 11.1 s on main-thread work while loading, 6.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 s of main-thread work and 671 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: 24
24/100Your mobile performance score is 24. 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, Accessibe Accessibility Overlay and Facebook and others), adding 1.8 MB and 2.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.3 s. During a long task the page ignores taps.
Use efficient cache lifetimes
500 ms · 415 KiB18 files are served with short cache lifetimes, so returning visitors download them again (415 KiB).
Improve image delivery
732 KiB14 images could be 732 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
500 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 500 ms.
Accessibe Accessibility Overlay adds 317 ms
317 msAccessibe Accessibility Overlay costs a phone 317 ms of main-thread work and 243 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 300 ms
300 msFacebook costs a phone 300 ms of main-thread work and 227 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.
Legacy JavaScript
150 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
152 KiBAbout 152 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
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: 31 ms
31 msYour server sent the HTML in 31 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.
First Contentful Paint: 9.0 s
9.0 sThe first text or image appears after 9.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 17.7 s
17.7 sYour largest element takes 17.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ICONICA DISCOVER MORE”.
Time to Interactive: 28.9 s
28.9 sThe page becomes fully interactive after 28.9 s. Good is under 3.8 s.
Speed Index: 15.0 s
15.0 sVisually, the page fills in at 15.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 4.1 s
4.1 sScripts block taps and scrolling for 4.1 s in total while the page loads. Good is under 200 ms.
Real-user TTFB: 978 ms
978 msReal visitors wait 978 ms for your server to start answering (75th percentile). Good is under 800 ms.
13 images without width and height
13 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-10-24, real Chrome visitors' tap response (inp) went from 331 ms to 329 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 173 ms
173 msReal visitors wait 173 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.2 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.083
0.083The layout barely moves while loading (CLS 0.083, good is under 0.1).
Images and page weight
Page weight: 7.6 MB in 137 requests
7.6 MBYour homepage downloads 7.6 MB in 137 requests on a phone: scripts 3.4 MB (35), media 2.8 MB (2) and images 1.0 MB (36). Under 2 MB keeps phones on slow connections fast.
9 images far larger than shown
586 KiB9 images are downloaded at several times the size a phone draws them, for example PBC5110_O1000_00000_10.jpg at 3,000 px wide, shown at 170 px. Resized copies would save about 586 KiB.
14 images below the first screen load straight away
14 images further down the page (749 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (58 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 2.2 g of CO₂ per visit
2.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.16 g of CO₂e: 259.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
41 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: 41 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “Pomellato Online Boutique | Jewelry - Rings, Earrings, Bracelets, Necklaces”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
69 internal links, 0 external
The homepage links to 69 pages on pomellato.com and 0 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Pomellato, the first global luxury Italian fashion fine jeweler. Shop online with free shipping our rings, bracelets, n…”.
Canonical URL set
The canonical URL is https://www.pomellato.com/.
Structured data in place
Structured data found: OnlineStore, 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.pomellato.com/sitemap/index.xml.
AI search readiness
Some text only appears after JavaScript runs
54%The HTML your server sends has 149 of the 275 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.pomellato.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.
2 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 contact details; sameAs (social profiles) and description would complete it.
Other pages
15 pages point its canonical at the homepage
https://www.pomellato.com/us_en/craftsmanship, https://www.pomellato.com/us_en/sustanibility, https://www.pomellato.com/us_en/about-pomellato, https://www.pomellato.com/us_en/latest-news, https://www.pomellato.com/us_en/pomellato-world and https://www.pomellato.com/us_en/pomellato-products/jewelry/discover-all and 9 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
16 pages share a title
https://www.pomellato.com/us_en, https://www.pomellato.com/us_en/craftsmanship, https://www.pomellato.com/us_en/sustanibility, https://www.pomellato.com/us_en/about-pomellato, https://www.pomellato.com/us_en/latest-news and https://www.pomellato.com/us_en/pomellato-world and 10 others all use the title “Pomellato Online Boutique | Jewelry - Rings, Earrings, Bracelets, Nec…”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://www.pomellato.com/us_en/craftsmanship, https://www.pomellato.com/us_en/sustanibility, https://www.pomellato.com/us_en/about-pomellato, https://www.pomellato.com/us_en/latest-news, https://www.pomellato.com/us_en/pomellato-world and https://www.pomellato.com/us_en/pomellato-products/jewelry/discover-all and 9 others use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.pomellato.com/us_en/craftsmanship, https://www.pomellato.com/us_en/sustanibility, https://www.pomellato.com/us_en/about-pomellato, https://www.pomellato.com/us_en/latest-news, https://www.pomellato.com/us_en/pomellato-world and https://www.pomellato.com/us_en/pomellato-products/jewelry/discover-all and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://www.pomellato.com/us_en/craftsmanship, https://www.pomellato.com/us_en/sustanibility, https://www.pomellato.com/us_en/about-pomellato, https://www.pomellato.com/us_en/latest-news, https://www.pomellato.com/us_en/pomellato-world and https://www.pomellato.com/us_en/pomellato-products/jewelry/discover-all and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
3 pages slow to respond
https://www.pomellato.com/us_en/pomellato-products/jewelry/earrings, https://www.pomellato.com/us_en/pomellato-products/jewelry/iconica and https://www.pomellato.com/us_en/pomellato-products/jewelry/nudo took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
7 small tap targets
7 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Minified React error #425; visit https://reactjs.org/docs/error-decoder.html?invariant=425 for the full message or use …”.
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
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 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 275 words of copy
The homepage carries about 275 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Microsoft Clarity (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
15 other companies contacted
Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 pomellato.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Vercel
Company
- Founded
- 1967
- Headquarters
- Milan
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on pomellato.com, including 19 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.