applegate.com website review

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

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

About 240 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Bugsnag and others), adding 7.1 MB and 2.1 s of main-thread time.

Google Tag Manager costs a phone 942 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.

jebbit.com costs a phone 132 ms of main-thread work and 3.9 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.

cloudfront.net costs a phone 376 ms of main-thread work and 868 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.

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

ZenDesk costs a phone 138 ms of main-thread work and 399 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 images could be 193 KiB 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

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

13 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 17 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.

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

Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “It Just Comes Naturally at Applegate”.

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

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

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

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

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

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

Your homepage downloads 8.2 MB in 154 requests on a phone: scripts 3.0 MB (50), media 2.0 MB (1) and images 1.8 MB (46). Under 2 MB keeps phones on slow connections fast.

4 images (208 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.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

1 image has no alt text, which hurts accessibility and image search.

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

5 elements have a tabindex above 0, which scrambles the keyboard order.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

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

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

The homepage links to 111 pages on applegate.com and 27 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.

/products, /locator, /mission, /recipes, /blog and /products/bacon/category and 9 others use the same meta description. A description written for each page earns more clicks.

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

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Mixed content”).

1 link from your homepage to your own site is broken, for example https://applegate.com/blog (500).

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

5 links go through two or more redirects, for example http://www.applegate.com/mission-report.

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

applegate.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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 317 words of visible text.

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 Ads, Google Analytics, Google Tag Manager and Hotjar (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 6 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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.