Website review, no card needed
nappadori.com website review
Visit site (opens in a new tab)Reviewed 4 November 202640 issues · 94 checks
This review found 40 issues worth fixing on nappadori.com, 13 of them high impact, across 94 checks. The most urgent: render-blocking requests. 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
81B- #39,309 of 116,154 reviewed websitesbeats 61%
- #26,503 of 66,742 online storesbeats 54%
- #25,576 of 60,922 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 135 ms |
| May 23, 2026 | 142 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 184 ms |
| Jun 13, 2026 | 186 ms |
| Jun 20, 2026 | 182 ms |
| Jun 27, 2026 | 168 ms |
| Jul 4, 2026 | 147 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 143 ms |
| Jul 25, 2026 | 142 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 143 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 149 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 157 ms |
| Sep 19, 2026 | 160 ms |
| Sep 26, 2026 | 161 ms |
| Oct 3, 2026 | 167 ms |
| Oct 10, 2026 | 174 ms |
| Oct 17, 2026 | 179 ms |
| Oct 24, 2026 | 184 ms |
| Oct 31, 2026 | 181 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.3 s
2.7 s
4.0 s
5.4 s
6.7 s
8.0 s
9.4 s
10.7 s
Speed
Render-blocking requests
1.4 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.2 s
A phone's processor spends 8.2 s on main-thread work while loading, 4.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (shiprocket.in, Google Tag Manager and YouTube and others), adding 3.8 MB and 2.5 s of main-thread time.
Reduce unused JavaScript
200 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 200 ms faster on a phone.
Improve image delivery
400 ms · 279 KiB12 images could be 279 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
shiprocket.in adds 564 ms
564 msshiprocket.in costs a phone 564 ms of main-thread work and 120 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.
YouTube adds 461 ms
461 msYouTube costs a phone 461 ms of main-thread work and 996 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.
Google Tag Manager adds 478 ms
478 msGoogle Tag Manager costs a phone 478 ms of main-thread work and 514 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.
Shopify adds 397 ms
397 msShopify costs a phone 397 ms of main-thread work and 1.2 MB 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.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 513 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
50 ms · 361 KiB26 files are served with short cache lifetimes, so returning visitors download them again (361 KiB).
razorpay.com adds 307 ms
307 msrazorpay.com costs a phone 307 ms of main-thread work and 904 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.
2,757 HTML elements
The page has 2,757 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 206 KiBAbout 206 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need.
Minify JavaScript
16 KiB16 KiB could be saved by minifying JavaScript.
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: 25 ms
25 msYour server sent the HTML in 25 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 33.1 s
33.1 sThe page becomes fully interactive after 33.1 s. Good is under 3.8 s.
Largest Contentful Paint: 8.8 s
8.8 sYour largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 953 ms
953 msScripts block taps and scrolling for 953 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 135 ms to 181 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
32 images without width and height
32 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 191 ms
191 msReal visitors wait 191 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 499 ms
499 msReal visitors wait 499 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 451 requests
6.3 MBYour homepage downloads 6.3 MB in 451 requests on a phone: scripts 2.8 MB (106), images 1.4 MB (78) and other files 1.4 MB (236). Under 2 MB keeps phones on slow connections fast.
5 images far larger than shown
651 KiB5 images are downloaded at several times the size a phone draws them, for example hyderabad_store_jpg_1.webp at 1,400 px wide, shown at 310 px. Resized copies would save about 651 KiB.
8 images in older formats
8 images (1.3 MB) 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.
An image on the first screen is lazy-loaded
Winder_mobile_home_page_hero_banner-11_1x1.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).
About 1.8 g of CO₂ per visit
1.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.78 g of CO₂e: 213.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
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. (2 elements).
2 checks passed
Every image has alt text
All 61 images in the HTML carry an alt attribute.
52 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: 52 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (197 characters)
Your meta description is 197 characters; Google truncates after about 160, so the end of your pitch is cut.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
170 internal links, 6 external
The homepage links to 170 pages on nappadori.com and 6 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Nappa Dori | Handcrafted Leather Goods & Luxury Trunks”.
Title: 55 characters
Your title is a healthy 55 characters: “Handcrafted Goods for Travel, Work & Life by Nappa Dori”.
Canonical URL set
The canonical URL is https://www.nappadori.com/.
Structured data in place
Structured data found: BreadcrumbList and Organization.
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.nappadori.com/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
58%The HTML your server sends has 535 of the 927 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://www.nappadori.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages slow to respond
https://www.nappadori.com/collections/bags, https://www.nappadori.com/collections/sling-bags and https://www.nappadori.com/collections/laptop-bags took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 80 found) and read each the way a search engine does.
7 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 a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
11 third-party cookies
11 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
74 of 85 tappable elements near the top are at least 24 px.
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 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 927 words of copy
The homepage carries about 927 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
4 calls to action
The homepage has 4 calls to action, for example “SHOP BY GENDER” and “SHOP ALL BEST SELLERS”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 15 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
47 other companies contacted
Loading the homepage contacts 47 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 nappadori.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
- Gatsby
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on nappadori.com, including 21 speed issues, 2 SEO issues and 1 conversion gap. 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.