Website review, no card needed

flavorgod.com logo

flavorgod.com website review

Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 91 checks

This review found 43 issues worth fixing on flavorgod.com, 12 of them high impact, across 91 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.8 s1.5 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.3 s
Jul 4, 20262.0 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
169 ms132 msMay 16Oct 31162 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026136 ms
May 23, 2026141 ms
May 30, 2026145 ms
Jun 6, 2026149 ms
Jun 13, 2026152 ms
Jun 20, 2026153 ms
Jun 27, 2026152 ms
Jul 4, 2026147 ms
Jul 11, 2026146 ms
Jul 18, 2026145 ms
Jul 25, 2026140 ms
Aug 1, 2026137 ms
Aug 8, 2026137 ms
Aug 15, 2026138 ms
Aug 22, 2026143 ms
Aug 29, 2026149 ms
Sep 5, 2026154 ms
Sep 12, 2026154 ms
Sep 19, 2026154 ms
Sep 26, 2026154 ms
Oct 3, 2026154 ms
Oct 10, 2026162 ms
Oct 17, 2026165 ms
Oct 24, 2026163 ms
Oct 31, 2026162 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

Full-page screenshot of flavorgod.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. flavorgod.com at 0.9 s0.9 s
  2. flavorgod.com at 1.7 s1.7 s
  3. flavorgod.com at 2.6 s2.6 s
  4. flavorgod.com at 3.5 s3.5 s
  5. flavorgod.com at 4.3 s4.3 s
  6. flavorgod.com at 5.2 s5.2 s
  7. flavorgod.com at 6.1 s6.1 s
  8. flavorgod.com at 7.0 s7.0 s

Speed

11 to fix54
  • Render-blocking requests

    1.1 s

    32 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • 4,282 HTML elements

    The page has 4,282 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Main-thread work: 4.2 s

    A phone's processor spends 4.2 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    450 ms · 508 KiB

    About 508 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Sentry, Shopify and rebuyengine.com and others), adding 1.7 MB and 770 ms of main-thread time.

  • Improve image delivery

    889 KiB

    41 images could be 889 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    100 ms · 422 KiB

    17 files are served with short cache lifetimes, so returning visitors download them again (422 KiB).

  • Sentry adds 251 ms

    251 ms

    Sentry costs a phone 251 ms of main-thread work and 35 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 185 ms

    185 ms

    Shopify costs a phone 185 ms of main-thread work and 355 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.

  • rebuyengine.com adds 145 ms

    145 ms

    rebuyengine.com costs a phone 145 ms of main-thread work and 520 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.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 134 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    52 KiB

    Polyfills for old browsers add 52 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    27 KiB

    About 27 KiB of CSS is downloaded but never applied on this page.

  • Duplicated JavaScript

    14 KiB

    14 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    13 KiB

    13 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: 14 ms

    14 ms

    Your server sent the HTML in 14 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix100
  • 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: 14.6 s

    14.6 s

    Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 22.5 s

    22.5 s

    The page becomes fully interactive after 22.5 s. Good is under 3.8 s.

  • Speed Index: 10.1 s

    10.1 s

    Visually, the page fills in at 10.1 s (Speed Index). Good is under 3.4 s.

  • Real-user FCP: 2.0 s

    2.0 s

    Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 84 images without width and height

    84 images have no width and height attributes, so the layout jumps as each one loads.

  • First Contentful Paint: 2.5 s

    2.5 s

    The first text or image appears after 2.5 s on a phone. Good is under 1.8 s.

  • Cumulative Layout Shift: 0.157

    0.157

    The layout shifts by 0.157 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) got 17% slower for real visitors

    +17%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 136 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

    Real visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 171 ms

    171 ms

    Real visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 26% faster for real visitors

    -26%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 162 ms

    162 ms

    Scripts block the page for only 162 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix52
  • Page weight: 6.3 MB in 476 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 476 requests on a phone: images 2.8 MB (82), scripts 1.6 MB (112) and other files 1.3 MB (226). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    FlavorGod_Create_Combo_Fall_Mobile.png 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).

  • 5 images in older formats

    5 images (821 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.

  • 17 images below the first screen load straight away

    17 images further down the page (823 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.78 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.78 g of CO₂e: 213.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9492
  • 14 text elements with low contrast

    14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • 12 links without text

    12 visible links have no text or label, so screen readers cannot say where they go.

  • Alternative text of images should not be repeated as text (21 elements)

    Alternative text of images should not be repeated as text: 21 elements on the page fail this check, rated minor by axe-core.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h5, h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 325 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9277
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “FlavorGod® Seasonings | All-Natural Spices & Gourmet Rubs – Flavor God”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “SHOP BY COLLECTION”). One clear main headline is easier for people and search engines.

  • Meta description is long (208 characters)

    Your meta description is 208 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("flavorgod.com")”.

  • 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.

  • 347 internal links, 25 external

    The homepage links to 347 pages on flavorgod.com and 25 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://flavorgod.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://flavorgod.com/sitemap.xml.

AI search readiness

100
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,806 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://flavorgod.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://flavorgod.com/pages/create-your-own-combo-pack, https://flavorgod.com/collections/all-flavors, https://flavorgod.com/collections/seasonings, https://flavorgod.com/collections/toppers, https://flavorgod.com/collections/ebook and https://flavorgod.com/collections/accessories and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://flavorgod.com/pages/store-locator, https://flavorgod.com/collections/all-flavors, https://flavorgod.com/collections/seasonings, https://flavorgod.com/collections/toppers, https://flavorgod.com/collections/rubs-and-finisher-salts and https://flavorgod.com/collections/limited-edition and 6 others 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 59 found) and read each the way a search engine does.

5 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.

  • 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

1 to fixGoogle 9293
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'product')”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    24 of 24 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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.

  • 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 1,225 words of copy

    The homepage carries about 1,225 words of visible text.

5 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Where To Buy”, “Contact” and “Learn More”.

  • 12 short forms

    12 short forms (3 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 108 testimonial or review blocks and a star rating.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag 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.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 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.

  • 56 other companies contacted

    Loading the homepage contacts 56 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 flavorgod.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 17 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Microsoft Clarity · Seo Manager Venntov · Sendlane Marketing Automation · Userway Website Accessibility · Judge Me Reviews · Frequently Bought · Smart Discounts · Page Speed Booster · Quick Link · Back In Stock · Freegifts · reamaze.com · cloudfront.net · bogos.io · goaffpro.com · rudderstack.com · rebuyengine.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
Los Angeles

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 flavorgod.com, including 20 speed issues, 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25