dyflexis.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and cookiebot.eu and others), adding 1.5 MB and 857 ms of main-thread time.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

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

Google CDN costs a phone 285 ms of main-thread work and 734 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,114 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

About 114 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.0 MB in 93 requests on a phone: scripts 1.6 MB (26), images 625 KiB (37) and other files 367 KiB (16). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (94 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 0.85 g of CO₂e: 102.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

28 elements hidden from screen readers can still receive keyboard focus.

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

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

The homepage links to 96 pages on dyflexis.com and 9 external pages.

/contact, /partnerprogram, /marketplace, /workforce-management/data-driven and /workforce-management/capacity-management have no meta description, so Google writes the search snippet from whatever text it finds.

/pricing has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://w.strds.nl/jq.png?id=3afc2d4c&c=%7B%22_stfv%22%3A1792746722.1655092%2C%22_gcl_au%22%3A%221.1.1547681649.1792746722%22%2C%22c%22%3A2%2C%22f%22%3A0%2C%22h%22%3A2%2C%22p%22%3A5%2C%22w%22%3A1%2C%2.

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

2 errors were logged to the browser console while the page loaded, for example “Loading the image 'https://cdn6.prppr.nl/jq6.png?i=265069326&c=3316080944' violates the following Content Security Poli…”.

Chrome logged issues while loading the page (“Content security policy”).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

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

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

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 916 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 Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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