mikeferry.com website review

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

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

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

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

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

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

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

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

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

Google CDN costs a phone 519 ms of main-thread work and 734 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.

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

Facebook costs a phone 333 ms of main-thread work and 227 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 349 ms. During a long task the page ignores taps.

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

43 KiB could be saved by minifying JavaScript.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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.

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.

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

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

Real visitors wait 3.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

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

Your homepage downloads 5.1 MB in 204 requests on a phone: scripts 2.1 MB (84), images 1.8 MB (15) and stylesheets 456 KiB (63). Under 2 MB keeps phones on slow connections fast.

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

9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (6 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 27 characters: “The Mike Ferry Organization”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 123 pages on mikeferry.com and 18 external pages.

There is no https://www.mikeferry.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.mikeferry.com/real-estate-coaching is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.mikeferry.com/neuro-linguistic-program-sls, whose canonical is https://www.mikeferry.com/neuro-linguistic-program-the-art-of-sales-persuasion-sls. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187048962&tm=gtm002&Ver=2&mid=4bde285b-0737-48f4-94cd-bd22af5eddb8&bo=1&sid=b9585130cf4811f1ba2c2365737e853e&vid=b9586c30cf4811f1b5a39b04b8efe773&vids=1&msclkid=N&gtm_.

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

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'appendChild')”.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (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 27 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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.