Website review, no card needed
naturesflavors.com website review
Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 90 checks
This review found 43 issues worth fixing on naturesflavors.com, 18 of them high impact, across 90 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
82B- #34,390 of 122,925 reviewed websitesbeats 67%
- #22,831 of 69,353 online storesbeats 61%
- #22,058 of 63,146 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 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.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 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 | 155 ms |
| May 23, 2026 | 150 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 142 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 183 ms |
| Jul 11, 2026 | 171 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 149 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 139 ms |
| Aug 15, 2026 | 142 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 142 ms |
| Oct 3, 2026 | 147 ms |
| Oct 10, 2026 | 153 ms |
| Oct 17, 2026 | 156 ms |
| Oct 24, 2026 | 154 ms |
| Oct 31, 2026 | 148 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
0.8 s
1.7 s
2.5 s
3.3 s
4.2 s
5.0 s
5.8 s
6.7 s
Speed
Render-blocking requests
1.2 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.2 s
A phone's processor spends 7.2 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,092 HTML elements
The page has 3,092 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 (frontapp.com, Google Tag Manager and Shopify and others), adding 3.7 MB and 1.8 s of main-thread time.
Reduce unused JavaScript
600 ms · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Improve image delivery
150 ms · 1.1 MB51 images could be 1.1 MB 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.
frontapp.com adds 536 ms
536 msfrontapp.com costs a phone 536 ms of main-thread work and 1.5 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.
Google Tag Manager adds 517 ms
517 msGoogle Tag Manager costs a phone 517 ms of main-thread work and 969 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.
Reduce unused CSS
450 ms · 115 KiBAbout 115 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 483 ms. During a long task the page ignores taps.
Shopify adds 246 ms
246 msShopify costs a phone 246 ms of main-thread work and 639 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.
Use efficient cache lifetimes
100 ms · 198 KiB15 files are served with short cache lifetimes, so returning visitors download them again (198 KiB).
Minify JavaScript
150 ms · 20 KiB20 KiB could be saved by minifying JavaScript.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
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: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 31.5 s
31.5 sThe page becomes fully interactive after 31.5 s. Good is under 3.8 s.
Largest Contentful Paint: 9.2 s
9.2 sYour largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Three amber glass flavor extract bottles labeled Apple's Fl…”.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 661 ms
661 msScripts block taps and scrolling for 661 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
28 images without width and height
28 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-31, real Chrome visitors' tap response (inp) went from 155 ms to 148 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 158 ms
158 msReal visitors wait 158 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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 551 ms
551 msReal visitors wait 551 ms for your server to start answering (75th percentile). Good is under 800 ms.
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: 7.5 MB in 485 requests
7.5 MBYour homepage downloads 7.5 MB in 485 requests on a phone: scripts 3.2 MB (216), images 2.0 MB (81) and fonts 992 KiB (4). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
nf-thanksgiving-three-flavors-2oz-banner-3f93d27c-1c74-4015- 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).
6 images in older formats
6 images (595 KiB) 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.
1 image far larger than shown
92 KiB1 image is downloaded at several times the size a phone draws it, for example OrganicMangoFlavorExtract96kb.jpg at 1,024 px wide, shown at 75 px. Resized copies would save about 92 KiB.
About 2.1 g of CO₂ per visit
2.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.11 g of CO₂e: 253.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
17 tap targets too small
17 tap targets are too small or too close together to hit reliably with a finger.
Form elements should have a visible label (4 elements)
Form elements should have a visible label: 4 elements on the page fail this check, rated serious by axe-core.
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.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (32 elements)
All page content should be contained by landmarks: 32 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (12 elements)
Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 11 failed. 8 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Natural Flavors, Flavor Extracts and Flavorings | Nature's Flavors”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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.
397 internal links, 9 external
The homepage links to 397 pages on naturesflavors.com and 9 external pages.
6 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Nature's Flavors produces natural food flavoring and organic flavors, which include extracts, concentrates, powders, oi…”.
One H1 headline
Your main headline reads: “Nature's Flavors”.
Canonical URL set
The canonical URL is https://www.naturesflavors.com/.
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.naturesflavors.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.naturesflavors.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.
Text is in the HTML
Your server sends the page's text in the HTML (1,710 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages are broken
Your homepage links to https://www.naturesflavors.com/collections/recipe-flavoring-resources and https://www.naturesflavors.com/collections/flavor-powders, which answer with an error. Visitors hit a dead end and search engines drop them.
6 pages without an H1
https://www.naturesflavors.com/collections/flavor-extracts, https://www.naturesflavors.com/collections/flavor-oils, https://www.naturesflavors.com/collections/flavor-concentrates, https://www.naturesflavors.com/collections/flavor-oil-for-lip-balm, https://www.naturesflavors.com/collections/syrups and https://www.naturesflavors.com/collections/flavored-syrups 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 136 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 6 pages that loaded have a meta description.
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 6 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=211061877&Ver=2&mid=214363bb-6399-4426-9dee-2e081dab1e18&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Natural%20Flavors,%20Flavor%20Extracts%20and%20Flavori.
52 small tap targets
52 of 172 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was 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 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 1,279 words of copy
The homepage carries about 1,279 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Holiday Flavors →” and “Shop Thanksgiving Flavors →”.
42 calls to action
The homepage has 42 calls to action, for example “Shop All Flavorings”, “Shop All Fragrances” and “Shop All Syrups”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 35 testimonial or review blocks, 1 customer or partner logo and a star rating.
Analytics in place
Analytics detected: Google Tag Manager and 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, Klaviyo and Microsoft Ads 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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
44 other companies contacted
Loading the homepage contacts 44 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 naturesflavors.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Yotpo Product Reviews · Yotpo Loyalty Rewards · Boost Ai Search Filter · Triplewhale · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · Swym Wishlist Plus · App Salespop · Upcart · route.com · luckyorange.com · archive-digger.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
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on naturesflavors.com, 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.