Website review, no card needed

mentalfloss.com logo

mentalfloss.com website review

Visit site (opens in a new tab)Reviewed 11 October 202633 issues · 82 checks

This review found 33 issues worth fixing on mentalfloss.com, 11 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.2 s1.9 sApr 18Oct 32.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.0 s
Apr 25, 20262.0 s
May 2, 20262.1 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.0 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
240 ms142 msApr 18Oct 3194 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026153 ms
Apr 25, 2026159 ms
May 2, 2026160 ms
May 9, 2026166 ms
May 16, 2026165 ms
May 23, 2026163 ms
May 30, 2026171 ms
Jun 6, 2026173 ms
Jun 13, 2026175 ms
Jun 20, 2026178 ms
Jun 27, 2026176 ms
Jul 4, 2026170 ms
Jul 11, 2026169 ms
Jul 18, 2026163 ms
Jul 25, 2026161 ms
Aug 1, 2026161 ms
Aug 8, 2026155 ms
Aug 15, 2026153 ms
Aug 22, 2026155 ms
Aug 29, 2026168 ms
Sep 5, 2026189 ms
Sep 12, 2026210 ms
Sep 19, 2026229 ms
Sep 26, 2026214 ms
Oct 3, 2026194 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of mentalfloss.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mentalfloss.com at 0.4 s0.4 s
  2. mentalfloss.com at 0.8 s0.8 s
  3. mentalfloss.com at 1.1 s1.1 s
  4. mentalfloss.com at 1.5 s1.5 s
  5. mentalfloss.com at 1.9 s1.9 s
  6. mentalfloss.com at 2.3 s2.3 s
  7. mentalfloss.com at 2.6 s2.6 s
  8. mentalfloss.com at 3.0 s3.0 s

Speed

12 to fix38
  • Use efficient cache lifetimes

    1.9 s · 1.7 MB

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

  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 5.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (minutemediacdn.com, Google Tag Manager and Optanon and others), adding 4.5 MB and 2.0 s of main-thread time.

  • Improve image delivery

    900 ms · 841 KiB

    23 images could be 841 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • minutemediacdn.com adds 675 ms

    675 ms

    minutemediacdn.com costs a phone 675 ms of main-thread work and 3.3 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused JavaScript

    300 ms · 619 KiB

    About 619 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 603 ms

    603 ms

    Google Tag Manager costs a phone 603 ms of main-thread work and 473 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Optanon adds 296 ms

    296 ms

    Optanon costs a phone 296 ms of main-thread work and 317 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    300 ms

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

  • 17 long tasks on the main thread

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

  • 2,075 HTML elements

    The page has 2,075 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused CSS

    46 KiB

    About 46 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    21 KiB

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

  • Phones get a much slower page than desktops

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

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 22 ms

    22 ms

    Your server sent the HTML in 22 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 11.5 s

    11.5 s

    Your largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 22.0 s

    22.0 s

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

  • First Contentful Paint: 6.0 s

    6.0 s

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

  • Speed Index: 7.4 s

    7.4 s

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

  • Total Blocking Time: 844 ms

    844 ms

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

  • Tap response (INP) got 31% slower for real visitors

    +31%

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

  • Largest content (LCP) got 10% slower for real visitors

    +10%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 111 ms

    111 ms

    Real visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 749 ms

    749 ms

    Real visitors wait 749 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 5.1 MB in 843 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 843 requests on a phone: scripts 2.6 MB (734), images 2.0 MB (73) and HTML 212 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    56 KiB

    1 image is downloaded at several times the size a phone draws it, for example images/voltaxMediaLibrary/mmsport/mentalfloss/01kvbew3rj6at3 at 2,000 px wide, shown at 390 px. Resized copies would save about 56 KiB.

  • 6 images below the first screen load straight away

    6 images further down the page (215 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.45 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

2 to fixGoogle 9497
  • 2 text elements with low contrast

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 71 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9294
  • Structured data has 7 problems

    Structured data found (BreadcrumbList, NewsArticle and WebSite) but with 7 problems, for example “NewsArticle: missing datePublished”.

  • 6 links with vague text

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

  • 175 internal links, 17 external

    The homepage links to 175 pages on mentalfloss.com and 17 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Learn weird, interesting facts about history, entertainment, language, geography, and more topics. Test your knowledge …”.

  • One H1 headline

    Your main headline reads: “The Mental Floss Newsletter”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Mental Floss - History, Trivia, Interesting Facts, and More”.

  • Canonical URL set

    The canonical URL is https://www.mentalfloss.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.mentalfloss.com/feed-sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

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

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,544 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.mentalfloss.com/llms.txt (12 KiB, 53 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.mentalfloss.com/mental-floss-newsletters, whose canonical is https://www.mentalfloss.com/about/mental-floss-newsletters. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.mentalfloss.com/amazingfactgenerator has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.mentalfloss.com/amazingfactgenerator has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 22 small tap targets

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

  • Deprecated browser APIs

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

  • 3 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

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

  • No direct contact details

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

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

  • About 1,466 words of copy

    The homepage carries about 1,466 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “SIGN UP” and “CONTACT US”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 4 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 43 cookies set on arrival

    43

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

  • 87 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mentalfloss.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager

Company

Founded
2001

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on mentalfloss.com, including 18 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25
mentalfloss.com website review: scores and fixes