folloze.com website review

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

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

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

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

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

posthog.com costs a phone 447 ms of main-thread work and 206 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.

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

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

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

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

11 KiB could be saved by minifying CSS.

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.

3 KiB JavaScript is shipped twice across bundles.

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.

Real visitors wait 836 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Target and convert your key accounts”.

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

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

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

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

11 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' tap response (inp) went from 355 ms to 411 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 178 requests on a phone: scripts 2.4 MB (55), fonts 368 KiB (10) and images 200 KiB (30). Under 2 MB keeps phones on slow connections fast.

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

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

Interactive controls must not be nested: 2 elements on the page fail 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.

4 visible links have no text or label, so screen readers cannot say where they go.

Your title is 85 characters, so Google will cut it off around 60: “Deliver Personalized Content with Folloze: Buyer Experience Platform for ABM at Scale”.

The homepage links to 45 pages on folloze.com and 18 external pages.

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

/folloze-ai 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 31 found) and read each the way a search engine does.

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'getAttribute')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Large scripts ship without source maps.

2 links to other sites are dead, for example https://www.g2.com/contributor/folloze-rl-25-vendor_self-30674077-0171-4eb2-b4d2-244fa51f5485?secure%5Bpage_id%5D=folloze-rl-25-vendor_self-30674077-0171-4eb2-b4d2-244fa51f5485&secure%5Brewards%5D=true&secure%5Btoken%5D=d965f65ae24cf8772c0ef3221279c0e2d6c1516a7c442139a6d51ede5e513fc7 (404).

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.

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.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

DMARC is set to p=none, so mail pretending to be folloze.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, Google Tag Manager, HubSpot and LinkedIn Insight (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 21 cookies (measured from a US location before any click).

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