Website review, no card needed
nori.co website review
Visit site (opens in a new tab)Reviewed 8 November 202630 issues · 80 checks
This review found 30 issues worth fixing on nori.co, 9 of them high impact, across 80 checks. The most urgent: page weight: 99.8 MB in 455 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
84B- #20,519 of 112,955 reviewed websitesbeats 77%
- #13,508 of 64,988 online storesbeats 73%
- #13,122 of 59,421 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 115 ms |
| May 23, 2026 | 121 ms |
| May 30, 2026 | 122 ms |
| Jun 6, 2026 | 127 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 127 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 117 ms |
| Jul 18, 2026 | 114 ms |
| Jul 25, 2026 | 116 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 114 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 119 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 114 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 105 ms |
| Oct 31, 2026 | 104 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
Use efficient cache lifetimes
1.9 s · 487 KiB42 files are served with short cache lifetimes, so returning visitors download them again (487 KiB).
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 2.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 (Google Tag Manager, Klaviyo and stylux.io and others), adding 1.9 MB and 1.2 s of main-thread time.
Reduce unused JavaScript
450 ms · 682 KiBAbout 682 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.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Google Tag Manager adds 366 ms
366 msGoogle Tag Manager costs a phone 366 ms of main-thread work and 530 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 189 ms
189 msKlaviyo costs a phone 189 ms of main-thread work and 361 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.
stylux.io adds 164 ms
164 msstylux.io costs a phone 164 ms of main-thread work and 333 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 116 ms
116 msShopify costs a phone 116 ms of main-thread work and 427 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 · 57 KiBPolyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 190 ms. During a long task the page ignores taps.
Improve image delivery
173 KiB7 images could be 173 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
22 KiBAbout 22 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
1 KiB1 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 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.
Time to Interactive: 22.7 s
22.7 sThe page becomes fully interactive after 22.7 s. Good is under 3.8 s.
Speed Index: 12.1 s
12.1 sVisually, the page fills in at 12.1 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a woman in a silver dress sitting on a cloud”.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 588 ms
588 msScripts block taps and scrolling for 588 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
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: 99 ms
99 msReal visitors wait 99 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 TTFB: 769 ms
769 msReal visitors wait 769 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 115 ms to 104 ms 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).
Images and page weight
Page weight: 99.8 MB in 455 requests
99.8 MBYour homepage downloads 99.8 MB in 455 requests on a phone: media 95.6 MB (12), scripts 1.9 MB (175) and other files 1.0 MB (185). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (73 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 28.3 g of CO₂ per visit
28.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 28.28 g of CO₂e: 3393.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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 (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (9 elements)
ARIA role should be appropriate for the element: 9 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 42 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 3 failed. 4 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.
Meta description is long (176 characters)
Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
45 internal links, 5 external
The homepage links to 45 pages on nori.co and 5 external pages.
5 checks passed
Title: 65 characters
Your title is a healthy 65 characters: “Nori - Best Steam Iron and Fabric Shaver for Clothes – Nori Press”.
Canonical URL set
The canonical URL is https://nori.co/.
Structured data in place
Structured data found: Organization and WebSite.
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://nori.co/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (813 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://nori.co/llms.txt (3 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://nori.co/pages/corporate-gifting, https://nori.co/pages/how-to-steam-2 and https://nori.co/pages/how-to-assemble have 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 24 found) and read each the way a search engine does.
6 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.
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
8 small tap targets
8 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Identifier 'heroToSliderEl' has already been declared”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 718 words of copy
The homepage carries about 718 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP THE NORI PRESS” and “SHOP THE NORI TRIM”.
11 calls to action
The homepage has 11 calls to action, for example “Shop All”, “Shop the Nori Press” and “Shop the Nori Trim”.
1 short form
A short form (0 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and “100,000+ Happy Customers”.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 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, Klaviyo 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.
27 cookies set on arrival
27Opening the homepage sets 27 cookies (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.
55 other companies contacted
Loading the homepage contacts 55 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 nori.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on nori.co, including 18 speed issues and 3 SEO issues. 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.