futuremethod.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user CLS: 0.39

  0.39

  For real visitors the layout shifts by 0.39 (75th percentile). Good is under 0.1.

• Real-user LCP: 2.7 s

  2.7 s

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

• Tap response (INP) held steady for real visitors

  +1%

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

• Page weight: 6.5 MB

  6.5 MB

  Your homepage downloads 6.5 MB on a phone, 2.5 MB of it images (39%). Under 2 MB keeps phones on slow connections fast.

• 1 image over 500 KB

  092A2196_-_Butt_Body_Scrub_740x800_64f3414f-1443-4a25-a63d-c weighs 1.3 MB. On a phone connection a single image that size takes seconds.

  Elements (1)

• 2 images far larger than shown

  1.3 MB

  2 images are downloaded at several times the size a phone draws them, for example 092A2196_-_Butt_Body_Scrub_740x800_64f3414f-1443-4a25-a63d-c at 4,081 px wide, shown at 135 px. Resized copies would save about 1.3 MB.

  Elements (2)

• 3 images below the first screen load straight away

  3 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (3)

• About 1.8 g of CO₂ per visit

  1.84 g

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

• 7 buttons without a name

  7 buttons have no accessible name, so screen readers announce just “button”.

  Elements (3)

• 7 tap targets too small

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

  Elements (3)

• 3 text elements with low contrast

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

  Elements (3)

• <html> element must have a lang attribute (1 element)

  <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• 38 images without alt text

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

  View sourceElements (3)

• All page content should be contained by landmarks (10 elements)

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

  Elements (3)

• Zoom is disabled

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

  Elements (1)

• 11 links without text

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

  Elements (3)

• 1 form field without a label

  1 form field has no label, so screen readers announce an empty box and autofill guesses.

  View source

• No page language

  The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

• Headings should not be empty (1 element)

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

  Elements (1)

• Headings skip levels

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

  View sourceElements (2)

• No H1 headline

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

• Structured data has 1 problem

  Structured data found (FAQPage) but with 1 problem, for example “ld+json block 2 is not valid JSON (Bad control character in string literal in JSON at position )”.

  View source

• No social preview image

  No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  View source

• 74 internal links, 19 external

  The homepage links to 74 pages on futuremethod.com and 19 external pages.

• No Organization structured data

  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.

  View source

• No llms.txt

  There is no https://futuremethod.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.

• 1 page without a meta description

  https://futuremethod.com/pages/find-a-store has no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (1)

• 2 pages without an H1

  https://futuremethod.com/pages/find-a-store and https://futuremethod.com/pages/referrals have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 22 small tap targets

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

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

• Thin social proof

  Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• About 1,234 words of copy

  The homepage carries about 1,234 words of visible text.

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

• 33 cookies set on arrival

  33

  Opening the homepage sets 33 cookies, 1 of them by other companies (measured from a US location before any click).

• No consent tool detected

  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.

• 47 other companies contacted

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