jjtaylor.com website review

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

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and userway.org and others), adding 1.7 MB and 1.0 s of main-thread time.

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

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

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

YouTube costs a phone 614 ms of main-thread work and 1,004 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.

Google Tag Manager costs a phone 353 ms of main-thread work and 556 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.2 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

6 KiB could be saved by minifying JavaScript.

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.

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

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.

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

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

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

Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies on our website to give you the most relevant…”.

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

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

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

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

Your homepage downloads 7.1 MB in 129 requests on a phone: images 4.4 MB (29), scripts 1.8 MB (43) and fonts 437 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is only 27 characters: “J.J. Taylor Companies, Inc.”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 5 <h1> headlines (“First Choice Beer Distributor”, “Your Trusted Beer Advisor” and “Ordering Online Made Easy”). One clear main headline is easier for people and search engines.

The homepage links to 43 pages on jjtaylor.com and 7 external pages.

There is no https://www.jjtaylor.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.

https://www.jjtaylor.com/career-openings is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.jjtaylor.com/florida-portfolio and https://www.jjtaylor.com/florida/florida-portfolio all use the title “J.J. Taylor Distributing Florida, Inc. Portfolio”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.jjtaylor.com/mission-vision-statement, https://www.jjtaylor.com/company-news, https://www.jjtaylor.com/career-openings and https://www.jjtaylor.com/charity have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jjtaylor.com/about-us and https://www.jjtaylor.com/contact-us use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.jjtaylor.com/florida/florida-portfolio, whose canonical is https://www.jjtaylor.com/florida-portfolio. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.jjtaylor.com/about-us, https://www.jjtaylor.com/supplier-news, https://www.jjtaylor.com/career-openings, https://www.jjtaylor.com/contact-us, https://www.jjtaylor.com/become-a-customer and https://www.jjtaylor.com/newsupplierrequestform have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.jjtaylor.com/mission-vision-statement, https://www.jjtaylor.com/about-us, https://www.jjtaylor.com/florida-portfolio, https://www.jjtaylor.com/supplier-news, https://www.jjtaylor.com/careers/for-your-growth and https://www.jjtaylor.com/career-openings and 3 others took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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 631 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, 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 12 cookies, 1 of them by other companies (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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.