functionalpatterns.com website review

30 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

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

route.com costs a phone 1.0 s of main-thread work and 1.1 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.

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

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

8 third-party services load with your homepage (route.com, Hotjar and Google Tag Manager and others), adding 4.1 MB and 2.7 s of main-thread time.

About 2.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

24 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

1.4 MB JavaScript is shipped twice across bundles.

Hotjar costs a phone 414 ms of main-thread work and 261 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 383 ms of main-thread work and 364 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 405 ms. During a long task the page ignores taps.

Klaviyo costs a phone 274 ms of main-thread work and 514 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.

emotivecdn.io costs a phone 182 ms of main-thread work and 384 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.

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

About 65 KiB of CSS is downloaded but never applied on this page.

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

11 KiB could be saved by minifying CSS.

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.

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 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

The layout shifts by 0.236 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 15.1 MB in 403 requests on a phone: media 4.9 MB (3), images 4.7 MB (77) and scripts 3.5 MB (127). Under 2 MB keeps phones on slow connections fast.

16 images are downloaded at several times the size a phone draws them, for example Ismael.png at 1,080 px wide, shown at 286 px. Resized copies would save about 669 KiB.

1 image (73 KiB) is 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 4.28 g of CO₂e: 514.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

28 form fields have no label, so screen readers announce an empty box and autofill guesses.

25 visible links have no text or label, so screen readers cannot say where they go.

ARIA role should be appropriate for the element: 29 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

There are 14 <h1> headlines (“”, “We help you move the way your body was designed.” and “Why Functional Patterns works when nothing else h…”). One clear main headline is easier for people and search engines.

Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected ',' or ']' after array element in JSON at position )”.

The homepage links to 98 pages on functionalpatterns.com and 7 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.

https://functionalpatterns.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://functionalpatterns.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://functionalpatterns.com/collections/equipment-accessories, https://functionalpatterns.com/customer_authentication/redirect, https://functionalpatterns.com/pages/get-certified, https://functionalpatterns.com/pages/human-foundations, https://functionalpatterns.com/pages/human-biomechanics-specialist and https://functionalpatterns.com/pages/results have no meta description, so Google writes the search snippet from whatever text it finds.

https://functionalpatterns.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://functionalpatterns.com/collections/equipment-accessories and https://functionalpatterns.com/collections/accessories have 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 40 found) and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://functionalpatterns.com/cdn/shop/t/338/assets/HelveticaLTPro-Bold.woff?v=56043' bec…”.

Requests the geolocation permission on page load.

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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 1,143 words of visible text.

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

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Hotjar 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 24 cookies, 2 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 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.