gatewayfirst.com website review

Your mobile performance score is 64 (desktop: 97). Pages that score under 90 lose visitors before the first paint.

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

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

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

8 third-party services load with your homepage (Google Tag Manager, Basis and SiteScout and others), adding 366 KiB and 330 ms of main-thread time.

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

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

1 image could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Desktop scores 97 but mobile only 64. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

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

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

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

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

Some list items are not inside a list.

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

Your title is only 14 characters: “Gateway | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.gatewayfirst.com/sitemap.txt, so Google discovers your pages only by following links.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 115 pages on gatewayfirst.com and 5 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.

/support, /personal/private-banking, /personal/trust-services and /personal/home-improvement-financing have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://use.typekit.net/vhg8lje.css' violates the following Content Security Policy directive: "connect-…”.

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

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

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

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

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

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

DMARC is set to p=none, so mail pretending to be gatewayfirst.com is still delivered. Reports are on, so moving to quarantine is the next step.

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.

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