mahoneyes.com website review

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

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

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

Google CDN costs a phone 1.4 s of main-thread work and 2.5 MB 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.

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Hubspot and others), adding 4.3 MB and 2.6 s of main-thread time.

10 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

FontAwesome CDN costs a phone 62 ms of main-thread work and 425 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.

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

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

4 KiB could be saved by minifying JavaScript.

3 KiB could be saved by minifying CSS.

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.57 (75th percentile). Good is under 0.1.

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

Your largest element takes 27.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To provide the best experiences, we use technologies like c…”.

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

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

Scripts block taps and scrolling for 1.0 s 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 78 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Real visitors wait 982 ms for your server to start answering (75th percentile). Good is under 800 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' largest content (lcp) went from 2.6 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.3 MB in 159 requests on a phone: scripts 4.3 MB (56), images 1.6 MB (37) and other files 726 KiB (27). Under 2 MB keeps phones on slow connections fast.

Mahoney-Commercial-Kitchen-Checklist-2.png weighs 582 KiB. On a phone connection a single image that size takes seconds.

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

1 image further down the page (582 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 2.06 g of CO₂e: 247.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

11 images have no alt text, which hurts accessibility and image search.

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

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

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

Your title is 69 characters, so Google will cut it off around 60: “Mahoney Environmental | Cooking Oil Collection & Grease Trap Services”.

There are 5 <h1> headlines (“Used Cooking Oil Collection & Recycling”, “Grease Trap Cleaning” and “Cooking Oil Equipment”). One clear main headline is easier for people and search engines.

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

The homepage links to 143 pages on mahoneyes.com and 14 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.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 images are served at too low a resolution for sharp phone screens.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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