jfpetrogroup.com website review

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

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

FontAwesome CDN costs a phone 1.4 s of main-thread work and 118 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (FontAwesome CDN, Google Tag Manager and Optanon and others), adding 762 KiB and 1.9 s of main-thread time.

Your mobile performance score is 51 (desktop: 40). Pages that score under 90 lose visitors before the first paint.

9 images could be 477 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

Google Tag Manager costs a phone 431 ms of main-thread work and 341 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.

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

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

Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need. 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 50 ms).

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.

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

Comp-1-5.mp4 weighs 1.0 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.9 MB in 185 requests on a phone: images 2.1 MB (50), scripts 997 KiB (56) and fonts 356 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

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

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

Elements must only use permitted ARIA attributes: 9 elements on the page fail this check, rated serious by axe-core.

ARIA commands must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.

4 text elements don'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.

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

Your title is only 15 characters: “Home - JF Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 117 pages on jfpetrogroup.com and 22 external pages.

There is no https://jfpetrogroup.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://jfpetrogroup.com/quote-request, https://jfpetrogroup.com/service-request, https://jfpetrogroup.com/who-we-are, https://jfpetrogroup.com/our-history, https://jfpetrogroup.com/leadership-team and https://jfpetrogroup.com/fueling-america and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://jfpetrogroup.com/quote-request, https://jfpetrogroup.com/service-request, https://jfpetrogroup.com/who-we-are, https://jfpetrogroup.com/our-history, https://jfpetrogroup.com/leadership-team and https://jfpetrogroup.com/fueling-america and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://jfpetrogroup.com/wp-content/uploads/2025/07/Comp-1-5.mp4.

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

2 errors were logged to the browser console while the page loaded, for example “EncodingError: The source image cannot be decoded.”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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 435 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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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