Website review, no card needed
nudora.com website review
Visit site (opens in a new tab)Reviewed 17 November 202631 issues · 77 checks
This review found 31 issues worth fixing on nudora.com, 8 of them high impact, across 77 checks. The most urgent: main-thread work: 7.3 s. 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
One score from every part of this review. How it works
Speed
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 2.9 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 (Shopify, TikTok and Klaviyo and others), adding 1.2 MB and 1.6 s of main-thread time.
Improve image delivery
950 ms · 183 KiB2 images could be 183 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Shopify adds 925 ms
925 msShopify costs a phone 925 ms of main-thread work and 647 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.
Render-blocking requests
800 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Reduce unused JavaScript
383 KiBAbout 383 KiB of JavaScript is downloaded but never used on this page.
2,923 HTML elements
The page has 2,923 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
100 ms · 152 KiB12 files are served with short cache lifetimes, so returning visitors download them again (152 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 150 ms. During a long task the page ignores taps.
Reduce unused CSS
63 KiBAbout 63 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).
Legacy JavaScript
39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need.
Minify JavaScript
6 KiB6 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: 24 ms
24 msYour server sent the HTML in 24 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 15.2 s
15.2 sThe page becomes fully interactive after 15.2 s. Good is under 3.8 s.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nudora wellness products”.
Total Blocking Time: 676 ms
676 msScripts block taps and scrolling for 676 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 2.7 MB in 284 requests
2.7 MBYour homepage downloads 2.7 MB in 284 requests on a phone: scripts 1.2 MB (150), other files 672 KiB (83) and images 414 KiB (8). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
D8676BF5-4E25-43F6-A430-51EF3F19B988.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 far larger than shown
130 KiB1 image is downloaded at several times the size a phone draws it, for example Nudora_Home_Hero.jpg at 1,800 px wide, shown at 358 px. Resized copies would save about 130 KiB.
About 0.8 g of CO₂ per visit
0.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 93.5 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
4 text elements with low contrast
4 text elements don'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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “Complete Wellness Support for Gut Health, Energy,…”). One clear main headline is easier for people and search engines.
Meta description is long (318 characters)
Your meta description is 318 characters; Google truncates after about 160, so the end of your pitch is cut.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
53 internal links, 11 external
The homepage links to 53 pages on nudora.com and 11 external pages.
6 checks passed
Title: 40 characters
Your title is a healthy 40 characters: “Nudora | Trust Your Gut – Nudora.com Inc”.
Canonical URL set
The canonical URL is https://nudora.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://nudora.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: 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,715 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://nudora.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://nudora.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://nudora.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
5 pages without a meta description
https://nudora.com/collections/all, https://nudora.com/customer_authentication/redirect, https://nudora.com/policies/shipping-policy, https://nudora.com/pages/hsa-fsa and https://nudora.com/pages/store-locator have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://nudora.com/collections/all, https://nudora.com/customer_authentication/redirect, https://nudora.com/collections/mtg-nudora, https://nudora.com/policies/shipping-policy, https://nudora.com/pages/hsa-fsa and https://nudora.com/pages/why-nudora and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://nudora.com/collections/mtg-nudora, https://nudora.com/policies/shipping-policy, https://nudora.com/pages/hsa-fsa, https://nudora.com/products/nudora-orange-2025, https://nudora.com/products/nudora-green-2025 and https://nudora.com/products/nudora-purple-2025 and 3 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.
8 pages slow to respond
https://nudora.com/pages/store-locator, https://nudora.com/products/nudora-orange-2025, https://nudora.com/products/nudora-green-2025, https://nudora.com/products/nudora-purple-2025, https://nudora.com/products/nudora-womens-hair-support and https://nudora.com/products/nudora-mens-hair-support and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.
3 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Unexpected token 'W', "W1tdLFt7Im"... is not valid JSON JSON.parse (<anonymous>)”.
Missing source maps
Large scripts ship without source maps.
1 low-resolution image
1 image is 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
5 of 5 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
About 1,001 words of copy
The homepage carries about 1,001 words of visible text.
3 checks passed
20 calls to action
The homepage has 20 calls to action, for example “Shop”, “Learn More” and “Shop Bundle”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo, Meta Pixel and Snap 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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
28 other companies contacted
Loading the homepage contacts 28 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 nudora.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Powerful Form Builder · Inbox · Reelup · snapchat.com · magefan.top · postscript.io
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
- 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 31 issues on nudora.com, including 12 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.