bitfactory.nl website review

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.4 s faster on a phone.

Vimeo costs a phone 1.4 s of main-thread work and 18.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

4 third-party services load with your homepage (Vimeo, Facebook and Hubspot and others), adding 19.0 MB and 2.0 s of main-thread time.

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

Facebook costs a phone 327 ms of main-thread work and 224 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 1,787 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google Fonts costs a phone 0 ms of main-thread work and 319 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.

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

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

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.

Your largest element takes 23.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Om de beste ervaringen te bieden, gebruiken wij technologie…”.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 20.5 MB in 143 requests on a phone: other files 15.7 MB (41), scripts 2.9 MB (34) and fonts 880 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

The homepage links to 201 pages on bitfactory.nl and 15 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) 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.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

Chrome logged issues while loading the page (“Cookie”).

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

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

X-XSS-Protection is set to “1”; 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.

bitfactory.nl 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.

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

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

Your longest form asks for 8 fields (6 required). Every extra field lowers completion.

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

DMARC is set to p=none, so mail pretending to be bitfactory.nl is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 HubSpot and Meta Pixel (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 13 cookies, 2 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.