fallon.com website review

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

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

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

5 third-party services load with your homepage (Google Tag Manager, Optanon and Google Analytics and others), adding 1.6 MB and 264 ms of main-thread time.

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

WordPress costs a phone 0 ms of main-thread work and 954 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.

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

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

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

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

Desktop scores 61 but mobile only 36. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

The layout shifts by 1.872 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To celebrate World Princess Week, we teamed up with Disney …”.

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

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

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

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

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 2.3 MB in 79 requests on a phone: images 1,001 KiB (40), scripts 674 KiB (15) and fonts 415 KiB (5). Under 2 MB keeps phones on slow connections fast.

1 image (31 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.

1 image further down the page (21 KiB) download before anyone scrolls to it. 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: 79.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 6 characters: “Fallon”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 11 characters: “Human Magic”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

There is no robots.txt at fallon.com/robots.txt, the first file search crawlers ask for.

The homepage links to only 3 pages on your own site, so visitors and crawlers find few routes into the rest of it.

A phone browser shows 1,314 words, but the HTML your server sends has only 25. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

/privacynotice has no meta description, so Google writes the search snippet from whatever text it finds.

/cookienotice and /privacynotice have no <h1> headline, so visitors and search engines get no clear main topic.

/cookienotice and /privacynotice have 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 2 pages linked from your homepage and read each the way a search engine does.

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

2 images are served at too low a resolution for sharp phone screens.

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.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 1,314 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 Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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