fandango.com website review

160 files are served with short cache lifetimes, so returning visitors download them again (3.6 MB).

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

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

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

8 third-party services load with your homepage (Google/Doubleclick Ads, DoubleVerify and Google Tag Manager and others), adding 1.9 MB and 1.6 s of main-thread time.

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

171 KiB could be saved by minifying JavaScript.

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

Google/Doubleclick Ads costs a phone 377 ms of main-thread work and 637 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.

DoubleVerify costs a phone 357 ms of main-thread work and 246 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.

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

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

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

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

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.

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.

Your largest element takes 25.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners also use tools on this site to provide …”.

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

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

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

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

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

16 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-03, real Chrome visitors' tap response (inp) went from 113 ms to 116 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 7.5 MB in 452 requests on a phone: scripts 3.5 MB (90), images 3.3 MB (155) and other files 270 KiB (173). Under 2 MB keeps phones on slow connections fast.

FAN_GWP_HeartOfTheBeast_DolbyUpgrade_1440x1152_V2_lg.jpg weighs 1.1 MB. On a phone connection a single image that size takes seconds.

13 images (2.7 MB) are 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.

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

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

5 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 19 elements on the page fail this check, rated minor by axe-core.

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

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

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

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 89 pages on fandango.com and 63 external pages.

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.

/ and /movietimes all use the title “Movie Tickets & Movie Times | Fandango”. Search engines can't tell which page to show for a search, so each competes with the others.

/movietimes and /offers use the same meta description. A description written for each page earns more clicks.

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

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

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

39 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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

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

http://fandango.com does not redirect to https, so some visitors land on the insecure version.

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

1 link go through two or more redirects, for example https://www.fandango.com/accounts/join-now?from=https%3A%2F%2Fwww.fandango.com%2F.

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.

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.

fandango.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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

The homepage carries about 747 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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 Comscore, Criteo, Google Ads, Google Tag Manager and Meta Pixel and 2 mores (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 29 cookies (measured from a US location before any click).

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