afry.com website review

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

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

About 223 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

3 third-party services load with your homepage (Google Tag Manager, intuitioncreative-52.com and YouTube), adding 202 KiB and 728 ms of main-thread time.

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

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

About 47 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

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

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

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 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We value your privacy We use cookies to help give you the b…”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 11.7 MB in 35 requests on a phone: media 9.2 MB (1), images 1.7 MB (12) and scripts 482 KiB (13). Under 2 MB keeps phones on slow connections fast.

gettyimages-2194140235_cropped.png weighs 941 KiB. On a phone connection a single image that size takes seconds.

5 images (1.3 MB) 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.

1 image is downloaded at several times the size a phone draws it, for example gettyimages-1359425105.jpg.webp at 2,560 px wide, shown at 390 px. Resized copies would save about 195 KiB.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

The homepage links to 248 pages on afry.com and 4 external pages.

Your Organization JSON-LD is missing url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

/en and /en-ca all use the title “Engineering, project management and advisory services | AFRY”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

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

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

X-XSS-Protection is set to “1; mode=block;”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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 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 1 cookie, 1 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.