Website review, no card needed

frontiercoop.com logo

frontiercoop.com website review

Visit site (opens in a new tab)Reviewed 4 November 202647 issues · 89 checks

This review found 47 issues worth fixing on frontiercoop.com, 22 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
3.2 s3.0 sMay 16Oct 313.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20263.1 s
Oct 17, 20263.2 s
Oct 24, 20263.1 s
Oct 31, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
131 ms108 msMay 16Oct 31125 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026111 ms
May 23, 2026111 ms
May 30, 2026111 ms
Jun 6, 2026111 ms
Jun 13, 2026112 ms
Jun 20, 2026113 ms
Jun 27, 2026113 ms
Jul 4, 2026116 ms
Jul 11, 2026115 ms
Jul 18, 2026115 ms
Jul 25, 2026114 ms
Aug 1, 2026113 ms
Aug 8, 2026114 ms
Aug 15, 2026117 ms
Aug 22, 2026117 ms
Aug 29, 2026116 ms
Sep 5, 2026118 ms
Sep 12, 2026120 ms
Sep 19, 2026120 ms
Sep 26, 2026121 ms
Oct 3, 2026125 ms
Oct 10, 2026125 ms
Oct 17, 2026128 ms
Oct 24, 2026128 ms
Oct 31, 2026125 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 frontiercoop.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. frontiercoop.com at 1.0 s1.0 s
  2. frontiercoop.com at 1.9 s1.9 s
  3. frontiercoop.com at 2.9 s2.9 s
  4. frontiercoop.com at 3.9 s3.9 s
  5. frontiercoop.com at 4.8 s4.8 s
  6. frontiercoop.com at 5.8 s5.8 s
  7. frontiercoop.com at 6.7 s6.7 s
  8. frontiercoop.com at 7.7 s7.7 s

Speed

12 to fix34
  • Use efficient cache lifetimes

    9.9 s · 78.6 MB

    34 files are served with short cache lifetimes, so returning visitors download them again (78.6 MB).

  • Reduce unused JavaScript

    9.9 s · 2.4 MB

    About 2.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.9 s faster on a phone.

  • Improve image delivery

    4.2 s · 715 KiB

    10 images could be 715 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.2 s faster on a phone.

  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.7 s

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

  • 3,677 HTML elements

    The page has 3,677 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 (Olark, widen.net and Klevu Search and others), adding 3.0 MB and 1.7 s of main-thread time.

  • Reduce unused CSS

    750 ms · 163 KiB

    About 163 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Render-blocking requests

    650 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • 20 long tasks on the main thread

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

  • widen.net adds 419 ms

    419 ms

    widen.net costs a phone 419 ms of main-thread work and 1.6 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.

  • Olark adds 428 ms

    428 ms

    Olark costs a phone 428 ms of main-thread work and 465 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.

  • Minify JavaScript

    150 ms · 4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 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 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 3.0 s

    3.0 s

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

  • Largest Contentful Paint: 31.0 s

    31.0 s

    Your largest element takes 31.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Frontier Spices & Vanilla, Shop Link to Holiday Favorites”.

  • Time to Interactive: 40.3 s

    40.3 s

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

  • Speed Index: 15.4 s

    15.4 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

    Scripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.8 s

    3.8 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 12 images without width and height

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

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

    +14%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

3 checks passed
  • Real-user INP: 124 ms

    124 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix35
  • Page weight: 83.8 MB in 342 requests

    83.8 MB

    Your homepage downloads 83.8 MB in 342 requests on a phone: media 76.5 MB (12), scripts 4.5 MB (120) and images 1.7 MB (38). Under 2 MB keeps phones on slow connections fast.

  • 5 images far larger than shown

    1.0 MB

    5 images are downloaded at several times the size a phone draws them, for example November-web-header-2345x3120.jpg at 2,345 px wide, shown at 294 px. Resized copies would save about 1.0 MB.

  • 1 image over 500 KB

    November-web-header-2345x3120.jpg weighs 517 KiB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (477 KiB) is 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 below the first screen load straight away

    1 image further down the page (42 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 23.7 g of CO₂ per visit

    23.75 g

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

Accessibility

7 to fixGoogle 9691
  • 13 tap targets too small

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

  • Hidden but focusable

    11 elements hidden from screen readers can still receive keyboard focus.

  • Interactive controls must not be nested (7 elements)

    Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 95 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

6 to fixGoogle 9270
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (82 characters)

    Your title is 82 characters, so Google will cut it off around 60: “Frontier Co-op: Sustainably Sourced Herbs, Spices, and Seasonings | Frontier Co-op”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 10 links with vague text

    10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 190 internal links, 17 external

    The homepage links to 190 pages on frontiercoop.com and 17 external pages.

3 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “We are Frontier Co-op – an ethically committed herb and spice company united by our mission to put people and planet be…”.

  • 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.frontiercoop.com/media/sitemap/frontiercoop_english/sitemap.xml.

AI search readiness

1 to fix88
  • 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.frontiercoop.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,297 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65
  • 2 linked pages are broken

    Your homepage links to https://www.frontiercoop.com/accessories/bulk-storage and https://www.frontiercoop.com/spices-and-seasonings/all-purpose, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages without a meta description

    https://www.frontiercoop.com/blog and https://www.frontiercoop.com/recipes have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.frontiercoop.com/storelocator, https://www.frontiercoop.com/blog and https://www.frontiercoop.com/recipes have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://www.frontiercoop.com/shipping-and-returns, https://www.frontiercoop.com/blog, https://www.frontiercoop.com/recipes, https://www.frontiercoop.com/about-us, https://www.frontiercoop.com/baking-and-cooking-ingredients and https://www.frontiercoop.com/spices-and-seasonings 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 90 found) and read each the way a search engine does.

4 checks passed
  • 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 9 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 71 small tap targets

    71 of 104 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_VERIFIER_CHANGED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 12 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 522 words of copy

    The homepage carries about 522 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Spices and Seasonings” and “Shop Bulk Products”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Shop Spices and Seasonings”, “Shop Bulk Products” and “Shop Herbs and Teas”.

  • 55 short forms

    55 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies (measured from a US location before any click).

  • 34 other companies contacted

    Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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 frontiercoop.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Magento
Analytics
Google Tag Manager
Hosting
AWS

Company

Founded
1976
Headquarters
Norway

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on frontiercoop.com, including 22 speed issues, 6 SEO issues and 2 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