Website review, no card needed
ghirelli.com website review
Visit site (opens in a new tab)Reviewed 13 November 202630 issues · 83 checks
This review found 30 issues worth fixing on ghirelli.com, 6 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. 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
87B- #7,602 of 108,947 reviewed websitesbeats 90%
- #4,453 of 61,775 online storesbeats 89%
- #4,327 of 56,370 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 106 ms |
| May 30, 2026 | 110 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 102 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 110 ms |
| Aug 15, 2026 | 109 ms |
| Aug 22, 2026 | 109 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 119 ms |
| Sep 12, 2026 | 119 ms |
| Sep 19, 2026 | 120 ms |
| Sep 26, 2026 | 113 ms |
| Oct 3, 2026 | 114 ms |
| Oct 10, 2026 | 116 ms |
| Oct 17, 2026 | 115 ms |
| Oct 24, 2026 | 113 ms |
| Oct 31, 2026 | 108 ms |
| Nov 7, 2026 | 101 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: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Improve image delivery
150 ms · 293 KiB13 images could be 293 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 729 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,238 HTML elements
The page has 2,238 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 (Klaviyo, Shopify and 506.io and others), adding 756 KiB and 363 ms of main-thread time.
Reduce unused JavaScript
243 KiBAbout 243 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
74 KiBPolyfills for old browsers add 74 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Use efficient cache lifetimes
43 KiB14 files are served with short cache lifetimes, so returning visitors download them again (43 KiB).
Reduce unused CSS
37 KiBAbout 37 KiB of CSS is downloaded but never applied on this page.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
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.
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ghirelli USA INC”.
Real-user TTFB: 913 ms
913 msReal visitors wait 913 ms for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 6.8 s
6.8 sThe page becomes fully interactive after 6.8 s. Good is under 3.8 s.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 106 ms to 101 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 121 ms
121 msReal visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 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-11-07, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.7 MB in 271 requests
3.7 MBYour homepage downloads 3.7 MB in 271 requests on a phone: images 1.7 MB (40), scripts 903 KiB (83) and other files 862 KiB (126). Under 2 MB keeps phones on slow connections fast.
14 images below the first screen load straight away
14 images further down the page (803 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
8 images far larger than shown
188 KiB8 images are downloaded at several times the size a phone draws them, for example G_Family_1.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 188 KiB.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
6 images without alt text
6 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.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails 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).
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
198 internal links, 4 external
The homepage links to 198 pages on ghirelli.com and 4 external pages.
8 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Ghirelli® has long been synonymous with beauty and excellence in the Rosary world. Handmade jewelry made In Italy. Disc…”.
One H1 headline
Your main headline reads: “Ghirelli USA INC”.
Title: 58 characters
Your title is a healthy 58 characters: “Ghirelli® Rosaries | Made in Italy Jewelry | Official Site”.
Canonical URL set
The canonical URL is https://ghirelli.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://ghirelli.com/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,661 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ghirelli.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://ghirelli.com/pages/800th-anniversary-of-st-francis-of-assisi, https://ghirelli.com/pages/the-usa-rosary-limited-edition-250th-anniversary, https://ghirelli.com/pages/rosalet%C2%AE-by-you, https://ghirelli.com/collections/new-in, https://ghirelli.com/collections/key-chain and https://ghirelli.com/pages/custom-rosary have no meta description, so Google writes the search snippet from whatever text it finds.
6 links to non-canonical URLs
Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://ghirelli.com/collections/modern-rosalet%C2%AE, whose canonical is https://ghirelli.com/collections/modern-rosalet%c2%ae. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://ghirelli.com/pages/800th-anniversary-of-st-francis-of-assisi, https://ghirelli.com/pages/the-usa-rosary-limited-edition-250th-anniversary, https://ghirelli.com/pages/rosalet%C2%AE-by-you and https://ghirelli.com/pages/custom-rosary 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 85 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.
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 15 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 682 words of copy
The homepage carries about 682 words of visible text.
4 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Shop by category”, “Shop by material” and “Shop now”.
16 short forms
16 short forms (1 field at most) are right on the homepage.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
26 other companies contacted
Loading the homepage contacts 26 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 ghirelli.com, 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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Uso Ultimate Special Offers · Klaviyo Email Marketing Sms · Eg Auto Add To Cart · Judge Me Reviews · Kickflip · cloudfront.net · 506.io · addons.business · pxucdn.com · useamp.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
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Blissfield
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on ghirelli.com, including 11 speed issues, 1 SEO issue 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.