abingdonoliveoilco.com website review

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

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

4 third-party services load with your homepage (Bigcommerce, Google Tag Manager and Google Fonts and others), adding 1.6 MB and 523 ms of main-thread time.

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

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

About 180 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

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

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

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

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

3 images are downloaded at several times the size a phone draws them, for example Spooky_Citrus_8.5_x_3.5_in_-_2.png at 2,000 px wide, shown at 390 px. Resized copies would save about 215 KiB.

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

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

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

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

2 links inside paragraphs rely on colour alone to stand out.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

69 links have no real href, so search engines can't follow them.

Your title is only 26 characters: “Abingdon Olive Oil Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

No XML sitemap at https://abingdonoliveoilco.com/sitemap.xml, so Google discovers your pages only by following links.

Your <h1> is empty.

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

The homepage links to 217 pages on abingdonoliveoilco.com and 10 external pages.

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.

There is no /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.

/categories, /ultra-premium-extra-virgin-olive-oils, /shop/fused-and-infused-olive-oils, /balsamics-dark, /balsamics-white and /shop/gourmet-oils and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /furry-friends-special-blend-JCV0, whose canonical is /furry-friends-special-blend. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://g.page/r/CUDGLLuKZcN6EB0/review.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

abingdonoliveoilco.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

abingdonoliveoilco.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 664 words of visible text.

DMARC is set to p=none, so mail pretending to be abingdonoliveoilco.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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.

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