freemanxp.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.3 MB and 1.3 s of main-thread time.

Google Tag Manager costs a phone 699 ms of main-thread work and 763 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 50 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 26.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We Make Moments That Matter”.

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

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

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

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

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

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

Your homepage downloads 13.7 MB in 130 requests on a phone: media 9.3 MB (1), images 2.4 MB (22) and scripts 1.7 MB (66). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example home-image-card.png at 1,296 px wide, shown at 351 px. Resized copies would save about 658 KiB.

8 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (377 KiB) is 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.

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

Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.

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

Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

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

The homepage links to 46 pages on freemanxp.com and 6 external pages.

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.

/about/press is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/event-services/strategy-insights, /case-studies, /about-us, /experience-events, /about/press and /intelligent-innovation and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134621207&tm=gtm002&Ver=2&mid=8a949e06-51fb-4e86-a70d-bd3d583a2606&bo=1&sid=d0663b50d34e11f18cec9ddaa46bf82b&vid=d06666d0d34e11f1bcee677756c8fb5f&vids=1&msclkid=N&pi=9.

3 of 12 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 “Failed to load resource: net::ERR_FAILED”.

1 link from your homepage to your own site is broken, for example https://www.freeman.com/case-studies/6-ways-amazon-struck-a-chord-at-newfronts/ (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.

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

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

Social proof on the homepage: 8 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 192 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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, Hotjar and LinkedIn Insight and 4 mores (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 25 cookies, 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.