ft700.net website review

The page goes through 2 redirects before it starts loading, costing about 7.1 s. Link and advertise the final URL directly.

23 images could be 1,014 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.3 s faster on a phone.

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

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

8 third-party services load with your homepage (fueltech.net, cloudfront.net and Shopify and others), adding 3.2 MB and 818 ms of main-thread time.

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

fueltech.net costs a phone 354 ms of main-thread work and 2.3 MB 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 74 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.

cloudfront.net costs a phone 287 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.

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

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

The HTML itself could arrive about 150 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

19 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

Your homepage downloads 4.1 MB in 287 requests on a phone: images 1.3 MB (43), scripts 1.2 MB (106) and other files 1,014 KiB (104). Under 2 MB keeps phones on slow connections fast.

CAMP_-_BN26_---Product-images_FT700_SAVE_1024x1024.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

3 images are downloaded at several times the size a phone draws them, for example CAMP_-_BN26_---Product-images_FT700_SAVE_1024x1024.png at 1,024 px wide, shown at 298 px. Resized copies would save about 43 KiB.

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

Images must have alternative text: 24 elements on the page fail this check, rated critical by axe-core.

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

2 links inside paragraphs rely on colour alone to stand out.

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

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

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

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

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

Your canonical URL points to fueltech.net, not ft700.net, so Google may credit that host instead.

Structured data found (Organization) but with 1 problem, for example “Organization: url points at a different host (https://www.fueltech.net)”.

8 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 215 pages on ft700.net and 44 external pages.

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

10 images failed to load on a phone, for example https://www.fueltech.net/products/undefined.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

Opening the homepage sets 11 cookies, 7 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.