futurebridge.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 LCP: 5.7 s

  5.7 s

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

• Real-user FCP: 5.2 s

  5.2 s

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

• Real-user TTFB: 3.8 s

  3.8 s

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

• Largest content (LCP) held steady for real visitors

  -4%

  Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.5 s to 5.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Page weight: 2.7 MB

  2.7 MB

  Your homepage downloads 2.7 MB on a phone, 892 KiB of it images (33%). Under 2 MB keeps phones on slow connections fast.

• 1 image far larger than shown

  48 KiB

  1 image is downloaded at several times the size a phone draws it, for example simens-energy.png at 954 px wide, shown at 150 px. Resized copies would save about 48 KiB.

  Elements (1)

• 2 images in older formats

  2 images (91 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.

  Elements (2)

• 3 images below the first screen load straight away

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

  Elements (3)

• About 0.8 g of CO₂ per visit

  0.76 g

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

• 18 text elements with low contrast

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

  Elements (3)

• Malformed lists

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

  Elements (1)

• Orphan list items

  Some list items are not inside a list.

  Elements (1)

• 1 tap target too small

  1 tap target is too small or too close together to hit reliably with a finger.

  Elements (1)

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

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

  Elements (3)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• Page should contain a level-one heading (1 element)

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

  Elements (1)

• 11 links without text

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

  Elements (3)

• 3 form fields without a label

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

  View source

• Headings skip levels

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

  View sourceElements (1)

• No H1 headline

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

• Meta description is long (217 characters)

  Your meta description is 217 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• 113 internal links, 11 external

  The homepage links to 113 pages on futurebridge.com and 11 external pages.

• 1 page without a meta description

  /solutions has no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (1)

• 1 page without an H1

  /solutions has 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 30 found) and read each the way a search engine does.

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.8.2/css/all.css' from origin 'https://www.futurebr…”.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  futurebridge.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  futurebridge.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• Thin social proof

  Social proof on the homepage: 29 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• 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 512 words of copy

  The homepage carries about 512 words of visible text.

• Email authentication score: 85/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 4 trackers load before any consent

  4

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

• 11 cookies set on arrival

  11

  Opening the homepage sets 11 cookies, 2 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.

• 26 other companies contacted

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