dataforest.ai website review

website-files.com costs a phone 1.5 s of main-thread work and 1.4 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.

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

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

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

The page has 3,715 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (website-files.com, Google Tag Manager and Facebook and others), adding 2.2 MB and 2.8 s of main-thread time.

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

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

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

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

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

Facebook costs a phone 273 ms of main-thread work and 223 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.

3 images could be 59 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 23 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.

Your largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A Team that delivers. Systems that perform. We help mid-siz…”.

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

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

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

Visually, the page fills in at 7.5 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 146 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.4 MB in 139 requests on a phone: scripts 1.1 MB (43), images 734 KiB (74) and other files 265 KiB (15). Under 2 MB keeps phones on slow connections fast.

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

1 dropdown has no label.

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

autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

The homepage links to 237 pages on dataforest.ai and 22 external pages.

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

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

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

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

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.

dataforest.ai 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.

dataforest.ai'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.

Your longest form asks for 10 fields (4 required). Every extra field lowers completion.

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 2,238 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, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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 9 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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.