Skip to content
Audit Complete

Results for https://infoplease.com

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 20:14 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)
D69

Site Health

Score: 69 / 100

Based on 8 categories, 0 sections

Room to improve — your 16.1s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Missing signals may be hurting your search visibility.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

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

Drupal · 284 peers
You 69
·
Avg 73
At average
0 50 100
Better than 2% of Drupal sites See full Drupal benchmark →
AngularJS · 326 peers
You 69
·
Avg 73
At average
0 50 100
Better than 7% of AngularJS sites See full AngularJS benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

HSTS header is missing

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

Security › Security Headers
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

is missing width/height — may cause layout shift

Performance issues directly impact user engagement and conversion rates.

Performance › Image Optimization
5

141 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
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%2Finfoplease.com)](https://beavercheck.com/results/7ac53666-c217-4965-9148-f410b78c6cf9)
<a href="https://beavercheck.com/results/7ac53666-c217-4965-9148-f410b78c6cf9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Finfoplease.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Finfoplease.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 16.1s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. The 3 security gaps leave your users exposed — modern browsers increasingly warn visitors about insecure sites. 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 16.1s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.
C
Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 7 warning

9 barrier(s) likely increasing bounce by ~31%.

Speed (2)

Page takes 16.1s to load

+12% bounce

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

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

Page feels frozen for 1.4s

+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 (4)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

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 (1)

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

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

Return on Investment

$550 investment → $0.77/month returns + USD 150,000 risk avoided

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

Investment

$550

6h · 5 findings

Monthly returns

$0.77 /mo

~$9.20 / year

  • Bandwidth savings $0.77

Regulatory risk avoided

USD 150,000

if kept compliant

  • ADA Title III USD 150,000

$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

$550

5.5 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

$12,501 / month at risk

~$150,009 / year if left unfixed

Compliance Risk

$150,000

ADA Title III
  • No <nav> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • Skip navigation link is missing (WCAG 2.4.1)
    ADA Title III: USD 25,000 – USD 150,000

Bandwidth Waste

$0.77 /mo

9584.6 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~958 KB per page load
    Saves $0.77/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 3 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.

37
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
93
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
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.

2.65 s

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

16.13 s

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

1.38 s

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

0.087

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

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

20.06 s

Detailed Report

Audit breakdown by category with detailed findings.

37

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.

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.

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
The first Earth Day was observed. div.daily-card > div.card-img-container > div.d-flex > img.img-fluid
www.infoplease.com/sites/infoplease.com/files/2019/04/04-22.jpg171.6 KiB162.4 KiB
Wizarding World of Harry Potter Castle by Carlos Cruz div.col-lg-6 > div.img-overlay-card > div.card-img-container > img.card-img
/sites/infoplease.com/files/2020-05/Wizarding_World_of_Ha...175.9 KiB159.3 KiB
Zodiac Signs div.col-sm-6 > div.img-overlay-card > div.card-img-container > img.card-img
www.infoplease.com/sites/infoplease.com/files/2020-05/Zodiac%20Signs.jpg173.5 KiB157.2 KiB
Genghis Khan div.col-sm-6 > div.img-overlay-card > div.card-img-container > img.card-img
www.infoplease.com/sites/infoplease.com/files/2021-09/Genghis%20Khan.jpeg98.3 KiB89.0 KiB
News of the world div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...88.3 KiB79.1 KiB
Antarctica div.col-sm-6 > div.img-overlay-card > div.card-img-container > img.card-img
www.infoplease.com/sites/infoplease.com/files/2021-08/Antarctica.jpeg59.4 KiB53.8 KiB
Isabella I div.daily-card > div.card-img-container > div.d-flex > img.img-fluid
www.infoplease.com/sites/infoplease.com/files/2019/04/04-22-Isabella-I.jpg44.1 KiB40.4 KiB
Waterfall div.img-overlay-card > div.card-img-container > picture > img.card-img
/sites/infoplease.com/files/styles/scale600w/public/2025-...54.5 KiB39.7 KiB
Canadian Flag div.col-sm-6 > div.img-overlay-card > div.card-img-container > img.card-img
www.infoplease.com/sites/infoplease.com/files/2022-05/iStock-486037941-min.jpg52.4 KiB36.4 KiB
The Seasons div.swiper-wrapper > div.swiper-slide > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/2025-...57.5 KiB34.0 KiB
div.card-img-container > div.d-flex > picture > img.img-fluid div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...30.6 KiB25.9 KiB
div.card-img-container > div.d-flex > picture > img.img-fluid div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...29.9 KiB25.4 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-12-IMG
nodeLabel: Quill and Book
path: 1,HTML,1,BODY,2,DIV,0,DIV,1,MAIN,1,DIV,0,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,1,DIV,0,PICTURE,1,IMG
selector: div.swiper-wrapper > div.swiper-slide > picture > img.img-fluid
snippet: <img src="https://www.infoplease.com/sites/infoplease.com/files/styles/scale800w/pub…" alt="Quill and Book" class="img-fluid position-absolute top-0 left-0 object-fit-cover w-100 h-100 z-n1" loading="lazy" decoding="async">

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

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: 814 ms
URLTime Spent
infoplease.com/814 ms
www.infoplease.com/0.0 ms

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.

Diagnostics

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.

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.

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 Evaluation4.0 s
Other877 ms
Style & Layout769 ms
Script Parsing & Compilation578 ms
Parse HTML & CSS215 ms
Rendering91 ms
Garbage Collection28 ms

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.

URL
The first Earth Day was observed. div.daily-card > div.card-img-container > div.d-flex > img.img-fluid
www.infoplease.com/sites/infoplease.com/files/2019/04/04-22.jpg
Isabella I div.daily-card > div.card-img-container > div.d-flex > img.img-fluid
www.infoplease.com/sites/infoplease.com/files/2019/04/04-22-Isabella-I.jpg
div.card-img-container > div.d-flex > picture > img.img-fluid div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...
div.card-img-container > div.d-flex > picture > img.img-fluid div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...
div.card-img-container > div.d-flex > picture > img.img-fluid div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...
News of the world div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...
Infoplease logo div.block > a.navbar-brand > div.navbar-brand__logo > img
www.infoplease.com/themes/custom/ip_radix/logo.svg
logo div.offcanvas-header > a.navbar-brand > div.navbar-brand__logo > img
www.infoplease.com/themes/custom/ip_radix/logo.svg
div.prefix-wrapper > span.field-prefix > div.voice-search-block > img div.prefix-wrapper > span.field-prefix > div.voice-search-block > img
www.infoplease.com/modules/contrib/custom_voice_search/images/mic.png
Playwire div.col-12 > div > a > img

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
User Timing marks and measures 10 user timings
Avoid long main-thread tasks 20 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 50 ms
Server Backend Latencies 110 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 2 layout shifts found
INP breakdown
Avoid non-composited animations
93

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.

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
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-12 > ul.social > li > a div.col-12 > ul.social > li > a
div.col-12 > ul.social > li > a div.col-12 > ul.social > li > a
div.col-12 > ul.social > li > a div.col-12 > ul.social > li > a

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
Check out more anniversaries div.view-content > div.daily-card > div.card-body > a.mt-auto
Learn More div.view-content > div.daily-card > div.card-body > a.mt-auto
Learn More div.view-content > div.daily-card > div.card-body > a.mt-auto
Guess Today's Analogy div.view-content > div.daily-card > div.card-body > a.mt-auto
More news of the day div.daily-card > div.card-body > div > a
2026 Current Events div.daily-card > div.card-body > div > a
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
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
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.
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.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
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.
77

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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
www.infoplease.com/ line 2197, col 8
ReferenceError: OBR is not defined at https://www.infoplease.com/:2198:9
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 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
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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
Links are crawlable
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

91
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
84
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
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.

817 ms

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

1.35 s

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

56 ms

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

0.015

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

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

3.44 s

Detailed Report

Audit breakdown by category with detailed findings.

91

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.

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.

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
The first Earth Day was observed. div.daily-card > div.card-img-container > div.d-flex > img.img-fluid
www.infoplease.com/sites/infoplease.com/files/2019/04/04-22.jpg171.6 KiB163.3 KiB
Wizarding World of Harry Potter Castle by Carlos Cruz div.col-lg-6 > div.img-overlay-card > div.card-img-container > img.card-img
/sites/infoplease.com/files/2020-05/Wizarding_World_of_Ha...175.9 KiB156.7 KiB
Zodiac Signs div.col-sm-6 > div.img-overlay-card > div.card-img-container > img.card-img
www.infoplease.com/sites/infoplease.com/files/2020-05/Zodiac%20Signs.jpg173.5 KiB154.5 KiB
Genghis Khan div.col-sm-6 > div.img-overlay-card > div.card-img-container > img.card-img
www.infoplease.com/sites/infoplease.com/files/2021-09/Genghis%20Khan.jpeg98.3 KiB84.9 KiB
News of the world div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...88.3 KiB80.0 KiB
Antarctica div.col-sm-6 > div.img-overlay-card > div.card-img-container > img.card-img
www.infoplease.com/sites/infoplease.com/files/2021-08/Antarctica.jpeg59.4 KiB51.3 KiB
Isabella I div.daily-card > div.card-img-container > div.d-flex > img.img-fluid
www.infoplease.com/sites/infoplease.com/files/2019/04/04-22-Isabella-I.jpg44.1 KiB40.7 KiB
Waterfall div.img-overlay-card > div.card-img-container > picture > img.card-img
/sites/infoplease.com/files/styles/scale600w/public/2025-...54.5 KiB39.7 KiB
Canadian Flag div.col-sm-6 > div.img-overlay-card > div.card-img-container > img.card-img
www.infoplease.com/sites/infoplease.com/files/2022-05/iStock-486037941-min.jpg52.4 KiB36.4 KiB
div.card-img-container > div.d-flex > picture > img.img-fluid div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...30.6 KiB26.4 KiB
div.card-img-container > div.d-flex > picture > img.img-fluid div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...29.9 KiB25.8 KiB
The Seasons div.swiper-wrapper > div.swiper-slide > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/2025-...57.5 KiB25.7 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-12-IMG
nodeLabel: Quill and Book
path: 1,HTML,1,BODY,2,DIV,0,DIV,1,MAIN,1,DIV,0,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,1,DIV,0,PICTURE,1,IMG
selector: div.swiper-wrapper > div.swiper-slide > picture > img.img-fluid
snippet: <img src="https://www.infoplease.com/sites/infoplease.com/files/styles/scale800w/pub…" alt="Quill and Book" class="img-fluid position-absolute top-0 left-0 object-fit-cover w-100 h-100 z-n1" loading="lazy" decoding="async">

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

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.

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: 254 ms
URLTime Spent
infoplease.com/254 ms
www.infoplease.com/0.0 ms

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

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.

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.

URL
The first Earth Day was observed. div.daily-card > div.card-img-container > div.d-flex > img.img-fluid
www.infoplease.com/sites/infoplease.com/files/2019/04/04-22.jpg
Isabella I div.daily-card > div.card-img-container > div.d-flex > img.img-fluid
www.infoplease.com/sites/infoplease.com/files/2019/04/04-22-Isabella-I.jpg
div.card-img-container > div.d-flex > picture > img.img-fluid div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...
div.card-img-container > div.d-flex > picture > img.img-fluid div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...
div.card-img-container > div.d-flex > picture > img.img-fluid div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...
News of the world div.card-img-container > div.d-flex > picture > img.img-fluid
/sites/infoplease.com/files/styles/scale800w/public/daily...
Infoplease logo div.block > a.navbar-brand > div.navbar-brand__logo > img
www.infoplease.com/themes/custom/ip_radix/logo.svg
div.prefix-wrapper > span.field-prefix > div.voice-search-block > img div.prefix-wrapper > span.field-prefix > div.voice-search-block > img
www.infoplease.com/modules/contrib/custom_voice_search/images/mic.png
facebook share icon ul.share-buttons > li > a.facebook > img
www.infoplease.com/modules/custom/custom_core_common/images/facebook.svg
twitter share icon ul.share-buttons > li > a.twitter > img
www.infoplease.com/modules/custom/custom_core_common/images/twitter.svg
Google bookmark icon ul.share-buttons > li > a.gbookmark > img
www.infoplease.com/modules/custom/custom_core_common/images/googlebookmarks.svg
email share icon ul.share-buttons > li > a.email > img
www.infoplease.com/modules/custom/custom_core_common/images/email.svg
Print page icon ul.share-buttons > li > a.print > img
www.infoplease.com/modules/custom/custom_core_common/images/print.svg
Playwire div.col-12 > div > a > img

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

Max Potential First Input Delay 110 ms
Layout shift culprits
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 10 user timings
JavaScript execution time 1.0 s
Minimizes main-thread work 1.7 s
Avoid long main-thread tasks 5 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 50 ms
Server Backend Latencies 310 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 30 ms
Avoid large layout shifts 4 layout shifts found
INP breakdown
Avoid non-composited animations
84

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

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
facebook share icon div#custom-core-share > ul.share-buttons > li > a.facebook
twitter share icon div#custom-core-share > ul.share-buttons > li > a.twitter
Google bookmark icon div#custom-core-share > ul.share-buttons > li > a.gbookmark
email share icon div#custom-core-share > ul.share-buttons > li > a.email
Print page icon div#custom-core-share > ul.share-buttons > li > a.print

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
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.prefix-wrapper > span.field-prefix > div.voice-search-block > img div.prefix-wrapper > span.field-prefix > div.voice-search-block > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-12 > ul.social > li > a div.col-12 > ul.social > li > a
div.col-12 > ul.social > li > a div.col-12 > ul.social > li > a
div.col-12 > ul.social > li > a div.col-12 > ul.social > li > a

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
Check out more anniversaries div.view-content > div.daily-card > div.card-body > a.mt-auto
Learn More div.view-content > div.daily-card > div.card-body > a.mt-auto
Learn More div.view-content > div.daily-card > div.card-body > a.mt-auto
Guess Today's Analogy div.view-content > div.daily-card > div.card-body > a.mt-auto
More news of the day div.daily-card > div.card-body > div > a
2026 Current Events div.daily-card > div.card-body > div > a
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Input buttons have discernible text.
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
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.
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.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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 type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
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.
77

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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
www.infoplease.com/ line 2197, col 8
ReferenceError: OBR is not defined at https://www.infoplease.com/:2198:9
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 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
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
85

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.prefix-wrapper > span.field-prefix > div.voice-search-block > img div.prefix-wrapper > span.field-prefix > div.voice-search-block > img

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

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
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback