Website review, no card needed

queencreekolivemill.com logo

queencreekolivemill.com website review

Visit site (opens in a new tab)Reviewed 7 November 202626 issues · 76 checks

This review found 26 issues worth fixing on queencreekolivemill.com, 7 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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
933 ms630 msMay 16Oct 31665 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026874 ms
May 23, 2026871 ms
May 30, 2026866 ms
Jun 6, 2026864 ms
Jun 13, 2026857 ms
Jun 20, 2026875 ms
Jun 27, 2026885 ms
Jul 4, 2026895 ms
Jul 11, 2026898 ms
Jul 18, 2026888 ms
Jul 25, 2026769 ms
Aug 1, 2026738 ms
Aug 8, 2026720 ms
Aug 15, 2026711 ms
Aug 22, 2026786 ms
Aug 29, 2026773 ms
Sep 5, 2026762 ms
Sep 12, 2026757 ms
Sep 19, 2026742 ms
Sep 26, 2026759 ms
Oct 3, 2026750 ms
Oct 10, 2026744 ms
Oct 17, 2026721 ms
Oct 24, 2026670 ms
Oct 31, 2026665 ms
Real-visitor tap response (INP)75th percentile, phones
116 ms83 msMay 16Oct 31105 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202687 ms
May 23, 202687 ms
May 30, 202688 ms
Jun 6, 202695 ms
Jun 13, 202696 ms
Jun 20, 202696 ms
Jun 27, 202699 ms
Jul 4, 202696 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 2026100 ms
Aug 1, 2026103 ms
Aug 8, 2026104 ms
Aug 15, 2026105 ms
Aug 22, 2026112 ms
Aug 29, 2026112 ms
Sep 5, 2026111 ms
Sep 12, 2026110 ms
Sep 19, 2026106 ms
Sep 26, 2026106 ms
Oct 3, 2026105 ms
Oct 10, 2026106 ms
Oct 17, 2026108 ms
Oct 24, 2026105 ms
Oct 31, 2026105 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 queencreekolivemill.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. queencreekolivemill.com at 0.5 s0.5 s
  2. queencreekolivemill.com at 1.0 s1.0 s
  3. queencreekolivemill.com at 1.5 s1.5 s
  4. queencreekolivemill.com at 2.0 s2.0 s
  5. queencreekolivemill.com at 2.5 s2.5 s
  6. queencreekolivemill.com at 3.0 s3.0 s
  7. queencreekolivemill.com at 3.5 s3.5 s
  8. queencreekolivemill.com at 4.0 s4.0 s

Speed

6 to fix59
  • Reduce unused JavaScript

    1.5 s · 302 KiB

    About 302 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 59

    59/100

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

  • Improve image delivery

    655 KiB

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

  • Use efficient cache lifetimes

    300 ms · 59 KiB

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

  • vitals.app adds 218 ms

    218 ms

    vitals.app costs a phone 218 ms of main-thread work and 440 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (vitals.app, Amazon Web Services and Shopify and others), adding 742 KiB and 356 ms of main-thread time.

  • Minify JavaScript

    150 ms · 29 KiB

    29 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    150 ms · 10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    32 KiB

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

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 750 ms of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 13.4 s

    13.4 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Time to Interactive: 13.7 s

    13.7 s

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

  • Speed Index: 6.6 s

    6.6 s

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

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

    +21%

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

9 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.2 s

    1.2 s

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

  • Real-user INP: 110 ms

    110 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 388 ms

    388 ms

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

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

    -23%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 19 ms

    19 ms

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

Images and page weight

2 to fix81
  • Page weight: 3.2 MB in 224 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 224 requests on a phone: images 1.3 MB (20), scripts 927 KiB (81) and other files 692 KiB (82). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Delicate_Balanced_Robust_Olive_Oil_Lifestyle_Resized.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).

  • About 0.9 g of CO₂ per visit

    0.90 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.1 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 to fixGoogle 9999
  • 14 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 21 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10083
  • Title is short (22 characters)

    Your title is only 22 characters: “Queen Creek Olive Mill”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 5 H1 headlines

    There are 5 <h1> headlines (“:root { --header-logo-width: 230px; }”, “Extra Virgin Olive Oil” and “Farm Fresh Dining”). One clear main headline is easier for people and search engines.

  • Meta description is long (224 characters)

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

  • 124 internal links, 11 external

    The homepage links to 124 pages on queencreekolivemill.com and 11 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.queencreekolivemill.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://www.queencreekolivemill.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: 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 (514 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix98
  • 11 pages share a meta description

    https://www.queencreekolivemill.com/collections/olive-oils, https://www.queencreekolivemill.com/collections/vinegars, https://www.queencreekolivemill.com/collections/stuffed-olives, https://www.queencreekolivemill.com/collections/pasta, https://www.queencreekolivemill.com/collections/honey-jams-mustards and https://www.queencreekolivemill.com/collections/sauces-sweets and 5 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 9285
  • 18 small tap targets

    18 of 45 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 “Identifier 'CartRemoveButton' has already been declared”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • Only about 164 words

    The homepage has only about 164 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW SHOP NOW”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “SHOP”, “Shop Now Shop Now” and “Contact Us”.

  • 2 short forms

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 12 cookies set on arrival

    12

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

  • 20 other companies contacted

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

Apps your storefront loads

Hulk Form Builder · Judge Me Reviews · Vitals · sealsubscriptions.com · activehosted.com · amazonaws.com · loopz.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

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Queen Creek

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on queencreekolivemill.com, including 11 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

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