Skip to content
Audit Complete

Results for https://ea.com

Visit site
Blog / Content · estimated Tracking: engaged readers
Spain Spain · Madrid Completed: Apr 16, 2026 17:24 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C74

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Adobe Fonts sites average 73
At average
Better than 60% of Adobe Fonts sites See full Adobe Fonts benchmark →
Apollo sites average 71
At average
Better than 69% of Apollo sites See full Apollo benchmark →

Top Priorities (5)

1

Cookie 'EDGESCAPE_COUNTRY' is missing the Secure flag

Security gaps expose your site and users to attacks, eroding trust.

Security › Cookie Security
2

Cookie 'EDGESCAPE_REGION' is missing the Secure flag

Security gaps expose your site and users to attacks, eroding trust.

Security › Cookie Security
3

Cookie 'EDGESCAPE_TIMEZONE' is missing the Secure flag

Security gaps expose your site and users to attacks, eroding trust.

Security › Cookie Security
4

Page weighs 10.0 MB (7.8 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

1 image-only link(s) without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fea.com)](https://beavercheck.com/results/17603ef1-73df-4886-b659-3051a27569d3)
<a href="https://beavercheck.com/results/17603ef1-73df-4886-b659-3051a27569d3"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fea.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fea.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 33.2s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 33.2s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.
B
Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~27%.

Speed (2)

Page takes 33.2s to load

+12% bounce

Users abandon at ~3s — you're 30.7s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 2.2s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

1 broken link(s) on the page

+2% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$500 investment → $1.97/month returns + USD 157,500 risk avoided

Payback period: > 2 years First-year ROI: -95%

Investment

$500

5h · 5 findings

Monthly returns

$1.97 /mo

~$24 / year

  • Bandwidth savings $1.97

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

$150 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$500

5.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,127 / month at risk

~$157,524 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+7 more

Bandwidth Waste

$1.97 /mo

24607.1 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~2.5 MB per page load
    Saves $1.97/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

34
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
87
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.94 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

33.24 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2.24 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.079

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

5.21 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

33.24 s

Detailed Report

Audit breakdown by category with detailed findings.

34

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/content/dam/ea/fc/fc-26/images/2026/01/fc26-tots-eacom-h...604800.0 s4.8 MiB
www.ea.com/resources/45db7e73769d85dee00da67fedb1d1da0d4e7c1c8df6b600.0 s62.5 KiB
/resources/45db7e73769d85dee00da67fedb1d1da0d4e7c1c8df6b/...600.0 s32.4 KiB
www.ea.com/newrelic.js322.0 s28.3 KiB
/content/dam/eacom/images/2023/09/ea-play-hero-gradient.p...604800.0 s234.7 KiB
www.ea.com/assets/fonts/text/ElectronicArtsText-Bold.woff23600.0 s28.4 KiB
www.ea.com/assets/fonts/text/ElectronicArtsText-Regular.woff23600.0 s27.3 KiB
www.ea.com/assets/fonts/display/ElectronicArtsDisplay-Bold.woff23600.0 s26.9 KiB
www.ea.com/assets/fonts/display/ElectronicArtsDisplay-Regular.woff23600.0 s26.4 KiB
/content/dam/eacom/commitments/common/ea-impact-report-20...604800.0 s200.7 KiB
/resources/45db7e73769d85dee00da67fedb1d1da0d4e7c1c8df6b/...600.0 s15.5 KiB
/content/dam/eacom/images/2024/09/eacom-ea-play-hero-md-g...604800.0 s114.1 KiB
/notice?domain=ea.com&c=teconsent&js=nj&noticeType=bb&tex...3600.0 s14.1 KiB
/content/dam/eacom/common/200429_global-nav/ea-medallion-...604800.0 s108.5 KiB
use.typekit.net/txn1klh.js600.0 s7.7 KiB
/resources/45db7e73769d85dee00da67fedb1d1da0d4e7c1c8df6b/...600.0 s6.6 KiB
/content/dam/eacom/common/ea-section-bg-hex-eaeaea-xl.png...604800.0 s34.3 KiB
w.soundcloud.com/player/api.js300.0 s3.5 KiB
/resources/45db7e73769d85dee00da67fedb1d1da0d4e7c1c8df6b/...600.0 s1.6 KiB
/content/dam/eacom/common/ea-section-bg-esrb-parents-blue...604800.0 s12.6 KiB
/content/dam/ea/fc/fc-26/tots/common/fc26-tots-horizontal...604800.0 s8.6 KiB
/1/f701a6c63c?a=149134891&sa=1&v=1209.f04e2b9&t=Unnamed%2...0.0 ms624 B
/content/dam/eacom/common/ea-wordmark-network-nav-coral.svg604800.0 s2.2 KiB
/content/dam/eacom/common/200429_global-nav/eaglobalnav-i...604800.0 s1.3 KiB
/content/dam/eacom/subscription/ea-play/common/hero-logos...604800.0 s1.1 KiB
/content/dam/eacom/common/200429_global-nav/eaglobalnav-i...604800.0 s1.1 KiB
/content/dam/eacom/common/200429_global-nav/eaglobalnav-i...604800.0 s826 B
/content/dam/eacom/common/200429_global-nav/eaglobalnav-i...604800.0 s825 B
media.contentapi.ea.com/content/dam/eacom/common/medallion-violet.png604800.0 s612 B
/p.gif?s=1&k=txn1klh&ht=tk&h=www.ea.com&f=7105.7106.7107....604800.0 s205 B

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
/af/61f808/00000000000000003b9b3d63/27/l?primer=f592e0a4b...70 ms
/af/9ec930/00000000000000003b9adf55/27/l?primer=f592e0a4b...70 ms
/af/ec8a3d/00000000000000003b9b136a/27/l?primer=f592e0a4b...65 ms
/af/422d60/00000000000000003b9b3d67/27/l?primer=f592e0a4b...65 ms
/af/76bc3b/00000000000000003b9b1369/27/l?primer=f592e0a4b...55 ms
/af/f2d2d8/000000000000000000012518/27/l?primer=f592e0a4b...55 ms
/af/acc12d/00000000000000003b9ad05b/27/l?primer=7cdcb44be...50 ms
/af/827015/000000000000000000011c3b/27/l?primer=f592e0a4b...45 ms
/af/2794cc/00000000000000003b9ad055/27/l?primer=7cdcb44be...45 ms
/af/9373a0/00000000000000003b9b3d68/27/l?primer=f592e0a4b...45 ms
/af/4c54ad/000000000000000000011c38/27/l?primer=f592e0a4b...40 ms
/af/5e9c68/00000000000000003b9ad05f/27/l?primer=7cdcb44be...40 ms
/af/ffb1e2/00000000000000003b9b3d64/27/l?primer=f592e0a4b...40 ms
/af/73b32b/00000000000000003b9ace35/27/l?primer=f592e0a4b...35 ms
/af/e49b47/00000000000000003b9ace2f/27/l?primer=f592e0a4b...35 ms
/af/1da05b/0000000000000000000132df/27/l?primer=f592e0a4b...30 ms
/af/f6c05e/00000000000000003b9b29b5/27/l?primer=f592e0a4b...30 ms
www.ea.com/assets/fonts/display/ElectronicArtsDisplay-Regular.woff225 ms
www.ea.com/assets/fonts/display/ElectronicArtsDisplay-Bold.woff225 ms
/af/2553b3/000000000000000000011c34/27/l?primer=f592e0a4b...25 ms
/af/031bc7/0000000000000000000132e5/27/l?primer=f592e0a4b...20 ms
www.ea.com/assets/fonts/text/ElectronicArtsText-Regular.woff215 ms
www.ea.com/assets/fonts/text/ElectronicArtsText-Bold.woff215 ms
/af/8f4e31/0000000000000000000132e3/27/l?primer=f592e0a4b...15 ms
/af/5a14d0/00000000000000003b9ace32/27/l?primer=f592e0a4b...10 ms
/af/30dcd5/00000000000000003b9ace2d/27/l?primer=f592e0a4b...10 ms
/af/8f2f8d/000000000000000000011c35/27/l?primer=f592e0a4b...10 ms
/af/6125b7/00000000000000003b9b29b2/27/l?primer=f592e0a4b...5.0 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
A golden football ornament placed against a vibrant blue background. div.eapl-hero__ratio > picture > img.eapl-hero__image
/content/dam/ea/fc/fc-26/images/2026/01/fc26-tots-eacom-h...4.8 MiB4.6 MiB
Image shows a Madden NFL player, two players from Football Club, and a Sims cha… picture > img
/content/dam/eacom/commitments/common/ea-impact-report-20...200.4 KiB149.1 KiB
div.eapl-hero__ratio > picture > img.eapl-hero__image div.eapl-hero__ratio > picture > img.eapl-hero__image
/content/dam/eacom/images/2024/09/eacom-ea-play-hero-md-g...113.8 KiB13.2 KiB
ea-network-legal > div#teconsent > a#icon-id0700976302464887 > ::before ea-network-legal > div#teconsent > a#icon-id0700976302464887 > ::before
consent.trustarc.com/get?name=privacy_choices_icon.png10.2 KiB8.5 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: A golden football ornament placed against a vibrant blue background.
path: 1,HTML,1,BODY,11,MAIN,1,EA-SECTION,0,EA-SECTION-COLUMN,0,EA-HERO,a,#document-fragment,1,DIV,2,PICTURE,5,IMG
selector: div.eapl-hero__ratio > picture > img.eapl-hero__image
snippet: <img class="eapl-hero__image eapl-animate__bg" src="https://media.contentapi.ea.com/content/dam/ea/fc/fc-26/images/2026/01/fc2…" alt="A golden football ornament placed against a vibrant blue background.">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 753 ms
URLTime Spent
ea.com/753 ms
www.ea.com/0.0 ms

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
www.ea.com/16.2 s3.7 s5.5 ms
Unattributable1.2 s20 ms0.0 ms
/release/4.69.4/elements/ea-age-gate-ea-age-gate-js~ea-al...881 ms778 ms10 ms
www.ea.com/resources/45db7e73769d85dee00da67fedb1d1da0d4e7c1c8df6b744 ms648 ms25 ms
/release/4.69.4/elements/ea-icons-ea-icons-js.727857f6.a9...581 ms471 ms15 ms
www.googletagmanager.com/gtm.js?id=GTM-TG32RCX250 ms216 ms30 ms
/release/4.69.4/elements/ea-tile-ea-tile-js.b365f041.656d...228 ms151 ms4.5 ms
/release/4.69.4/elements/ea-regional-pricing-selector-ea-...196 ms183 ms0.6 ms
/release/4.69.4/elements/ea-locale-selector-ea-locale-sel...191 ms170 ms4.6 ms
/release/4.69.4/elements/ea-network-nav-ea-network-nav-js...167 ms163 ms2.0 ms
/release/4.69.4/elements/ea-player-ea-player-js.b365f041....151 ms144 ms1.0 ms
www.googletagmanager.com/gtm.js?id=GTM-NC64XZB&gtm=4e64f0h1&bs=ctrl142 ms112 ms23 ms
/release/4.69.4/elements/ea-link-ea-link-js.b365f041.2987...134 ms131 ms0.9 ms
/release/4.69.4/elements/eacom-icons-eacom-icons-js.f3846...127 ms104 ms2.2 ms
/notice?domain=ea.com&c=teconsent&js=nj&noticeType=bb&tex...106 ms94 ms3.8 ms
/release/4.69.4/elements/ea-local-footer-ea-local-footer-...102 ms79 ms21 ms
/release/4.69.4/elements/ea-behaviors-ea-catalog-js~ea-bo...101 ms95 ms2.1 ms
/1/f701a6c63c?a=149134891&sa=1&v=1209.f04e2b9&t=Unnamed%2...87 ms85 ms0.4 ms
/release/4.69.4/elements/ea-hero-ea-hero-js.b365f041.8d7d...84 ms78 ms3.7 ms
/release/4.69.4/elements/ea-grid-ea-grid-js.31ecd969.5e35...77 ms72 ms2.6 ms
/release/4.69.4/elements/ea-local-footer-ea-local-footer-...76 ms64 ms3.7 ms
/release/4.69.4/elements/ea-type-kit-ea-type-kit-js.c2981...71 ms69 ms0.6 ms
/resources/45db7e73769d85dee00da67fedb1d1da0d4e7c1c8df6b/...69 ms61 ms5.8 ms
/release/4.69.4/elements/ea-date-field-ea-date-field-js.3...68 ms50 ms0.7 ms
/release/4.69.4/elements/ea-local-nav-advanced-ea-local-n...66 ms1.3 ms3.1 ms
/release/4.69.4/elements/ea-modal-ea-modal-js.b365f041.a7...63 ms54 ms1.5 ms
consent.trustarc.com/asset/notice.js/v/v1.7-172958 ms40 ms11 ms
/release/4.69.4/elements/ea-content-loader-ea-content-loa...53 ms49 ms0.4 ms
/release/4.69.4/elements/ea-player-ratings-detail-view-mc...52 ms47 ms1.7 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation8.4 s
Other8.2 s
Style & Layout3.1 s
Rendering2.4 s
Garbage Collection320 ms
Script Parsing & Compilation266 ms
Parse HTML & CSS146 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
The page has an unload handler in a sub frame.Actionable

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 26.2 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 7 animated elements found
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 120 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 40 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
User Timing marks and measures
87

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Battlefield 6 span.eapl-game-box__side-toggle
FC 26 span.eapl-game-box__side-toggle
EA SPORTS™ College Football 26 span.eapl-game-box__side-toggle
The Sims 4 span.eapl-game-box__side-toggle
Apex Legends span.eapl-game-box__side-toggle

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy and Cookie Policy div#truste-consent-text > p > span.no-gpc-detected > a#truste-privacy-button

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Experience unlimited access to a collection of top EA titles, trials of select … div.eapl-hero__content > h6.eapl-hero__body

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Austria Belgium Bulgaria Croatia Cyprus Czech Republic Denmark Estonia Finland … select#select
United States United Kingdom Australia France Deutschland Italia 日本 Polska Bras… select#select

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Your Privacy Choices ea-network-footer > ea-network-legal > div#teconsent > a#icon-id0700976302464887
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
a.eapl-text__toggle-link a.eapl-text__toggle-link
a.eapl-text__toggle-link
a.eapl-text__toggle-link a.eapl-text__toggle-link
a.eapl-text__toggle-link
a.eapl-text__toggle-link a.eapl-text__toggle-link
a.eapl-text__toggle-link
a.eapl-text__toggle-link a.eapl-text__toggle-link
a.eapl-text__toggle-link
a.eapl-text__toggle-link
a.eapl-text__toggle-link

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

48
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

900 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

9.73 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

96 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

1.067

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.26 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

9.73 s

Detailed Report

Audit breakdown by category with detailed findings.

48

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/content/dam/ea/fc/fc-26/images/2026/01/fc26-tots-eacom-h...604800.0 s5.2 MiB
/content/dam/ea/fc/fc-26/images/2026/01/fc26-tots-eacom-h...604800.0 s4.4 MiB
/content/dam/eacom/images/2023/09/ea-play-hero-gradient.p...604800.0 s593.4 KiB
/content/dam/eacom/images/2023/09/ea-play-hero-gradient.p...604800.0 s530.9 KiB
/content/dam/eacom/commitments/common/ea-impact-report-20...604800.0 s291.1 KiB
/content/dam/eacom/commitments/common/ea-impact-report-20...604800.0 s291.1 KiB
www.ea.com/newrelic.js256.0 s28.3 KiB
www.ea.com/assets/fonts/text/ElectronicArtsText-Bold.woff23600.0 s28.4 KiB
www.ea.com/assets/fonts/text/ElectronicArtsText-Light.woff23600.0 s27.5 KiB
www.ea.com/assets/fonts/text/ElectronicArtsText-Regular.woff23600.0 s27.3 KiB
www.ea.com/assets/fonts/display/ElectronicArtsDisplay-Bold.woff23600.0 s26.9 KiB
www.ea.com/assets/fonts/display/ElectronicArtsDisplay-Regular.woff23600.0 s26.4 KiB
/content/dam/gin/images/2025/04/cfb26-keyart.jpg.adapt.cr...604800.0 s143.3 KiB
/content/dam/eacom/images/2024/09/eacom-ea-play-hero-md-g...604800.0 s135.7 KiB
/content/dam/eacom/images/2024/09/eacom-ea-play-hero-md-g...604800.0 s117.1 KiB
/notice?domain=ea.com&c=teconsent&js=nj&noticeType=bb&tex...3600.0 s14.1 KiB
/content/dam/eacom/common/200429_global-nav/ea-medallion-...604800.0 s108.5 KiB
/content/dam/gin/images/2025/07/fc-26-key-art.jpg.adapt.c...604800.0 s93.1 KiB
/content/dam/gin/images/2025/08/bf6-box-art-1x1.jpg.adapt...604800.0 s88.5 KiB
use.typekit.net/txn1klh.js600.0 s7.7 KiB
/content/dam/eacom/common/ea-section-bg-hex-eaeaea-xl.png...604800.0 s54.7 KiB
/content/dam/eacom/common/ea-section-bg-hex-eaeaea-xl.png...604800.0 s34.1 KiB
w.soundcloud.com/player/api.js300.0 s3.5 KiB
/content/dam/eacom/common/ea-section-bg-esrb-parents-blue...604800.0 s30.4 KiB
/content/dam/eacom/common/ea-section-bg-esrb-parents-blue...604800.0 s30.4 KiB
/1/f701a6c63c?a=149134891&sa=1&v=1209.f04e2b9&t=Unnamed%2...0.0 ms1.0 KiB
/content/dam/ea/fc/fc-26/tots/common/fc26-tots-horizontal...604800.0 s8.6 KiB
/content/dam/eacom/common/ea-wordmark-network-nav-coral.svg604800.0 s2.2 KiB
/content/dam/eacom/common/200429_global-nav/eaglobalnav-i...604800.0 s1.3 KiB
/content/dam/eacom/subscription/ea-play/common/hero-logos...604800.0 s1.1 KiB
/content/dam/eacom/common/200429_global-nav/eaglobalnav-i...604800.0 s1.1 KiB
/content/dam/eacom/common/200429_global-nav/eaglobalnav-i...604800.0 s826 B
/content/dam/eacom/common/200429_global-nav/eaglobalnav-i...604800.0 s825 B
media.contentapi.ea.com/content/dam/eacom/common/medallion-violet.png604800.0 s612 B
/p.gif?s=1&k=txn1klh&ht=tk&h=www.ea.com&f=7105.7106.7107....604800.0 s205 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:1.0673679999999999] map[node:map[boundingRect:map[bottom:4169 height:4169 left:0 right:1350 top:0 width:1350] lhId:page-10-BODY nodeLabel:body path:1,HTML,1,BODY selector:body snippet:<body> type:node] score:0.791852 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:84 height:32 left:70 right:248 top:52 width:178] lhId:page-107-IMG nodeLabel:Electronics Arts Home path:1,HTML,1,BODY,10,EA-LOCAL-NAV-ADVANCED,a,#document-fragment,1,DIV,0,DIV,3,A,1,IMG selector:div.eapl-local-nav__shelf > div.eapl-local-nav__shelf-header > a.eapl-local-nav__shelf-home-link > img.eapl-local-nav__shelf-logo snippet:<img class="eapl-local-nav__shelf-logo" src="https://media.contentapi.ea.com/content/dam/eacom/common/ea-wordmark-netwo…" alt="Electronics Arts Home"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:3774 height:3774 left:0 right:1350 top:0 width:1350] lhId:page-9-MAIN nodeLabel:How our teams and creativity are shaping the stories, connections, and communit… path:1,HTML,1,BODY,11,MAIN selector:body > main snippet:<main> type:node] score:0.181603 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:84 height:32 left:70 right:248 top:52 width:178] lhId:page-107-IMG nodeLabel:Electronics Arts Home path:1,HTML,1,BODY,10,EA-LOCAL-NAV-ADVANCED,a,#document-fragment,1,DIV,0,DIV,3,A,1,IMG selector:div.eapl-local-nav__shelf > div.eapl-local-nav__shelf-header > a.eapl-local-nav__shelf-home-link > img.eapl-local-nav__shelf-logo snippet:<img class="eapl-local-nav__shelf-logo" src="https://media.contentapi.ea.com/content/dam/eacom/common/ea-wordmark-netwo…" alt="Electronics Arts Home"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:4169 height:4169 left:0 right:1350 top:0 width:1350] lhId:page-10-BODY nodeLabel:body path:1,HTML,1,BODY selector:body snippet:<body> type:node] score:0.062465 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:636 height:540 left:0 right:1350 top:96 width:1350] lhId:page-0-IMG nodeLabel:A golden football ornament placed against a vibrant blue background. path:1,HTML,1,BODY,11,MAIN,1,EA-SECTION,0,EA-SECTION-COLUMN,0,EA-HERO,a,#document-fragment,1,DIV,2,PICTURE,5,IMG selector:div.eapl-hero__ratio > picture > img.eapl-hero__image snippet:<img class="eapl-hero__image eapl-animate__bg" src="https://media.contentapi.ea.com/content/dam/ea/fc/fc-26/images/2026/01/fc2…" alt="A golden football ornament placed against a vibrant blue background."> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:940 height:900 left:0 right:1350 top:40 width:1350] lhId:page-11-EA-LOCAL-NAV-ADVANCED nodeLabel:Electronics Arts Home path:1,HTML,1,BODY,10,EA-LOCAL-NAV-ADVANCED selector:body > ea-local-nav-advanced.eapl-local-nav-mini snippet:<ea-local-nav-advanced home-text="Electronic Arts Home" home-tooltip="Electronic Arts Home" home-link="https://www.ea.com/" logo-image="https://media.contentapi.ea.com/content/dam/eacom/common/ea-wordmark-netwo…" logo-tooltip="Electronics Arts Home" theme="dark" shelf-type="band" open-drawer-text="Menu" close-drawer-text="Close" mini="" show-franchise-nav="" show-breadcrumbs="" franchise-link-text="All Games" franchise-link-url="/games" class="eapl-local-nav-mini net-nav-onscreen" is-desktop="" show-open-link=""> type:node] score:0.031448 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:636 height:540 left:0 right:1350 top:96 width:1350] lhId:page-0-IMG nodeLabel:A golden football ornament placed against a vibrant blue background. path:1,HTML,1,BODY,11,MAIN,1,EA-SECTION,0,EA-SECTION-COLUMN,0,EA-HERO,a,#document-fragment,1,DIV,2,PICTURE,5,IMG selector:div.eapl-hero__ratio > picture > img.eapl-hero__image snippet:<img class="eapl-hero__image eapl-animate__bg" src="https://media.contentapi.ea.com/content/dam/ea/fc/fc-26/images/2026/01/fc2…" alt="A golden football ornament placed against a vibrant blue background."> type:node]]] type:subitems]]]

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
/af/422d60/00000000000000003b9b3d67/27/l?primer=f592e0a4b...70 ms
/af/ffb1e2/00000000000000003b9b3d64/27/l?primer=f592e0a4b...70 ms
/af/9ec930/00000000000000003b9adf55/27/l?primer=f592e0a4b...70 ms
/af/ec8a3d/00000000000000003b9b136a/27/l?primer=f592e0a4b...65 ms
/af/9373a0/00000000000000003b9b3d68/27/l?primer=f592e0a4b...65 ms
/af/61f808/00000000000000003b9b3d63/27/l?primer=f592e0a4b...60 ms
/af/76bc3b/00000000000000003b9b1369/27/l?primer=f592e0a4b...40 ms
/af/f2d2d8/000000000000000000012518/27/l?primer=f592e0a4b...40 ms
/af/73b32b/00000000000000003b9ace35/27/l?primer=f592e0a4b...35 ms
/af/1da05b/0000000000000000000132df/27/l?primer=f592e0a4b...35 ms
/af/4c54ad/000000000000000000011c38/27/l?primer=f592e0a4b...35 ms
/af/f6c05e/00000000000000003b9b29b5/27/l?primer=f592e0a4b...30 ms
/af/2553b3/000000000000000000011c34/27/l?primer=f592e0a4b...30 ms
/af/031bc7/0000000000000000000132e5/27/l?primer=f592e0a4b...25 ms
/af/acc12d/00000000000000003b9ad05b/27/l?primer=7cdcb44be...25 ms
www.ea.com/assets/fonts/text/ElectronicArtsText-Bold.woff220 ms
www.ea.com/assets/fonts/display/ElectronicArtsDisplay-Regular.woff220 ms
www.ea.com/assets/fonts/text/ElectronicArtsText-Light.woff220 ms
/af/6125b7/00000000000000003b9b29b2/27/l?primer=f592e0a4b...20 ms
/af/8f2f8d/000000000000000000011c35/27/l?primer=f592e0a4b...20 ms
/af/2794cc/00000000000000003b9ad055/27/l?primer=7cdcb44be...20 ms
www.ea.com/assets/fonts/text/ElectronicArtsText-Regular.woff215 ms
www.ea.com/assets/fonts/display/ElectronicArtsDisplay-Bold.woff215 ms
/af/827015/000000000000000000011c3b/27/l?primer=f592e0a4b...15 ms
/af/41bb90/00000000000000003b9ace44/27/l?primer=f592e0a4b...10 ms
/af/e49b47/00000000000000003b9ace2f/27/l?primer=f592e0a4b...10 ms
/af/8f4e31/0000000000000000000132e3/27/l?primer=f592e0a4b...10 ms
/af/5e9c68/00000000000000003b9ad05f/27/l?primer=7cdcb44be...10 ms
/af/064c42/00000000000000003b9ace31/27/l?primer=f592e0a4b...5.0 ms
/af/5a14d0/00000000000000003b9ace32/27/l?primer=f592e0a4b...5.0 ms
/af/30dcd5/00000000000000003b9ace2d/27/l?primer=f592e0a4b...5.0 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
A golden football ornament placed against a vibrant blue background. div.eapl-hero__ratio > picture > img.eapl-hero__image
/content/dam/ea/fc/fc-26/images/2026/01/fc26-tots-eacom-h...4.4 MiB4.3 MiB
div.eapl-hero__ratio > picture > img.eapl-hero__image div.eapl-hero__ratio > picture > img.eapl-hero__image
/content/dam/eacom/images/2023/09/ea-play-hero-gradient.p...530.4 KiB411.7 KiB
Image shows a Madden NFL player, two players from Football Club, and a Sims cha… picture > img
/content/dam/eacom/commitments/common/ea-impact-report-20...290.7 KiB245.7 KiB
a#backgroundLink > ea-lazy-image > img.eapl-game-box__background-image a#backgroundLink > ea-lazy-image > img.eapl-game-box__background-image
/content/dam/gin/images/2025/04/cfb26-keyart.jpg.adapt.cr...143.1 KiB121.4 KiB
a#backgroundLink > ea-lazy-image > img.eapl-game-box__background-image a#backgroundLink > ea-lazy-image > img.eapl-game-box__background-image
/content/dam/gin/images/2025/07/fc-26-key-art.jpg.adapt.c...92.9 KiB71.9 KiB
a#backgroundLink > ea-lazy-image > img.eapl-game-box__background-image a#backgroundLink > ea-lazy-image > img.eapl-game-box__background-image
/content/dam/gin/images/2025/08/bf6-box-art-1x1.jpg.adapt...88.2 KiB68.3 KiB
div.eapl-hero__ratio > picture > img.eapl-hero__image div.eapl-hero__ratio > picture > img.eapl-hero__image
/content/dam/eacom/images/2024/09/eacom-ea-play-hero-md-g...116.8 KiB16.3 KiB
div.eapl-section > picture > img.eapl-section__background-image div.eapl-section > picture > img.eapl-section__background-image
/content/dam/eacom/common/ea-section-bg-esrb-parents-blue...30.1 KiB15.2 KiB
ea-network-legal > div#teconsent > a#icon-id04894766028178861 > ::before ea-network-legal > div#teconsent > a#icon-id04894766028178861 > ::before
consent.trustarc.com/get?name=privacy_choices_icon.png10.2 KiB8.5 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: A golden football ornament placed against a vibrant blue background.
path: 1,HTML,1,BODY,11,MAIN,1,EA-SECTION,0,EA-SECTION-COLUMN,0,EA-HERO,a,#document-fragment,1,DIV,2,PICTURE,5,IMG
selector: div.eapl-hero__ratio > picture > img.eapl-hero__image
snippet: <img class="eapl-hero__image eapl-animate__bg" src="https://media.contentapi.ea.com/content/dam/ea/fc/fc-26/images/2026/01/fc2…" alt="A golden football ornament placed against a vibrant blue background.">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 203 ms
URLTime Spent
ea.com/203 ms
www.ea.com/0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
body body
0.792
How our teams and creativity are shaping the stories, connections, and communit… body > main
0.182
body body
0.062
Electronics Arts Home body > ea-local-nav-advanced.eapl-local-nav-mini
0.031

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Other2.1 s
Script Evaluation1.6 s
Style & Layout771 ms
Rendering605 ms
Script Parsing & Compilation61 ms
Garbage Collection51 ms
Parse HTML & CSS36 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 24.5 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

More information about the performance of your application. These numbers don't directly affect the Performance score.

Max Potential First Input Delay 130 ms
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
JavaScript execution time 1.1 s
Avoid long main-thread tasks 2 long tasks found
Avoid non-composited animations 6 animated elements found
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 130 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
INP breakdown
User Timing marks and measures
92

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Battlefield 6 span.eapl-game-box__side-toggle
FC 26 span.eapl-game-box__side-toggle
EA SPORTS™ College Football 26 span.eapl-game-box__side-toggle
The Sims 4 span.eapl-game-box__side-toggle
Apex Legends span.eapl-game-box__side-toggle

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy and Cookie Policy div#truste-consent-text > p > span.no-gpc-detected > a#truste-privacy-button

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Experience unlimited access to a collection of top EA titles, trials of select … div.eapl-hero__content > h6.eapl-hero__body

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Your Privacy Choices ea-network-footer > ea-network-legal > div#teconsent > a#icon-id04894766028178861
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Identical links have the same purpose.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
www.ea.com/newrelic.js line 1, col 26938
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
a.eapl-text__toggle-link a.eapl-text__toggle-link
a.eapl-text__toggle-link
a.eapl-text__toggle-link a.eapl-text__toggle-link
a.eapl-text__toggle-link
a.eapl-text__toggle-link a.eapl-text__toggle-link
a.eapl-text__toggle-link
a.eapl-text__toggle-link a.eapl-text__toggle-link
a.eapl-text__toggle-link
a.eapl-text__toggle-link
a.eapl-text__toggle-link

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback