mainepointe.com website review

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

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

About 127 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 620 ms faster on a phone.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

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

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

4 third-party services load with your homepage (Google Tag Manager, ahrefs.com and Google Fonts and others), adding 318 KiB and 251 ms of main-thread time.

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

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 block taps and scrolling for 2.3 s in total while the page loads. Good is under 200 ms.

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

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The #1 supply chain consulting firm in the world.”. Most of its time is element render delay (2.2 s).

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

2 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-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 images are downloaded at several times the size a phone draws them, for example cnbc.png at 2,400 px wide, shown at 64 px. Resized copies would save about 246 KiB.

3 images (281 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 0.26 g of CO₂e: 30.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Some list items are not inside a list.

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

The homepage links to 46 pages on mainepointe.com and 5 external pages.

https://mainepointe.com/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

Large scripts ship without source maps.

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

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 1,624 words of visible text.

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 2 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.