Website review, no card needed
bostonglobe.com website review
Visit site (opens in a new tab)Reviewed 11 October 202639 issues · 95 checks
This review found 39 issues worth fixing on bostonglobe.com, 18 of them high impact, across 95 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 2.2 s |
| Apr 25, 2026 | 2.2 s |
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 121 ms |
| Apr 25, 2026 | 121 ms |
| May 2, 2026 | 121 ms |
| May 9, 2026 | 121 ms |
| May 16, 2026 | 122 ms |
| May 23, 2026 | 125 ms |
| May 30, 2026 | 128 ms |
| Jun 6, 2026 | 130 ms |
| Jun 13, 2026 | 134 ms |
| Jun 20, 2026 | 136 ms |
| Jun 27, 2026 | 135 ms |
| Jul 4, 2026 | 135 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 134 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 133 ms |
| Aug 8, 2026 | 130 ms |
| Aug 15, 2026 | 129 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 130 ms |
| Sep 12, 2026 | 135 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 142 ms |
| Oct 3, 2026 | 145 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
How it loaded on a phone
0.8 s
1.6 s
2.3 s
3.1 s
3.9 s
4.7 s
5.5 s
6.2 s
Speed
Reduce unused JavaScript
5.6 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.6 s faster on a phone.
Use efficient cache lifetimes
3.2 s · 1,002 KiB44 files are served with short cache lifetimes, so returning visitors download them again (1,002 KiB).
Render-blocking requests
2.8 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Mobile performance score: 28
28/100Your mobile performance score is 28 (desktop: 27). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.5 s
A phone's processor spends 6.5 s on main-thread work while loading, 4.4 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 (script.ac, Optanon and blueconic.net and others), adding 1.1 MB and 2.4 s of main-thread time.
Improve image delivery
200 ms · 644 KiB14 images could be 644 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
script.ac adds 821 ms
821 msscript.ac costs a phone 821 ms of main-thread work and 82 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.
Legacy JavaScript
400 ms · 75 KiBPolyfills for old browsers add 75 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
Optanon adds 427 ms
427 msOptanon costs a phone 427 ms of main-thread work and 291 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.
blueconic.net adds 359 ms
359 msblueconic.net costs a phone 359 ms of main-thread work and 95 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 342 ms. During a long task the page ignores taps.
2,346 HTML elements
The page has 2,346 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Reduce unused CSS
97 KiBAbout 97 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
41 KiB41 KiB could be saved by minifying JavaScript.
Minify CSS
13 KiB13 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 339 ms
339 msYour server sent the HTML in 339 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 19.4 s
19.4 sYour largest element takes 19.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Patriots receiver DeMario Douglas had two touchdown recepti…”.
Time to Interactive: 31.2 s
31.2 sThe page becomes fully interactive after 31.2 s. Good is under 3.8 s.
Speed Index: 14.6 s
14.6 sVisually, the page fills in at 14.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.7 s
6.7 sThe first text or image appears after 6.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
33 images without width and height
33 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 121 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.2 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.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 446 ms
446 msReal visitors wait 446 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.075
0.075The layout barely moves while loading (CLS 0.075, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 214 requests
5.2 MBYour homepage downloads 5.2 MB in 214 requests on a phone: scripts 2.7 MB (51), images 1.4 MB (55) and HTML 650 KiB (3). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
U3MHF7FVFCSXUQYU7UAPSR7NA4.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images below the first screen load straight away
2 images further down the page (53 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.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.47 g of CO₂e: 175.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Heading levels should only increase by one (27 elements)
Heading levels should only increase by one: 27 elements on the page fail this check, rated moderate by axe-core.
All page content should be contained by landmarks (24 elements)
All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (42 elements).
2 checks passed
Every image has alt text
All 5 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: missing name”.
128 internal links, 29 external
The homepage links to 128 pages on bostonglobe.com and 29 external pages.
6 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “New England’s largest news organization delivering trusted news, analysis, and insight for more than 150 years. Become …”.
Title: 55 characters
Your title is a healthy 55 characters: “The Boston Globe | New England news, weather and sports”.
Canonical URL set
The canonical URL is https://www.bostonglobe.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.bostonglobe.com/arc/outboundfeeds/news-sitemap/?outputType=xml.
AI search readiness
Most text only appears after JavaScript runs
15%A phone browser shows 2,592 words, but the HTML your server sends has only 400. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No llms.txt
There is no https://www.bostonglobe.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
2 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives url, logo, sameAs (social profiles) and contact details; name and description would complete it.
Other pages
1 page without a meta description
https://www.bostonglobe.com/metro/transportation has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.bostonglobe.com/sports/tv-radio, whose canonical is https://www.bostonglobe.com/sports/tvradio/listings. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages without an H1
https://www.bostonglobe.com/sports, https://www.bostonglobe.com/sports/baseball/redsox, https://www.bostonglobe.com/sports/football/patriots, https://www.bostonglobe.com/sports/basketball/celtics, https://www.bostonglobe.com/sports/hockey/bruins and https://www.bostonglobe.com/sports/high-schools and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.bostonglobe.com/sports/tv-radio, https://www.bostonglobe.com/metro/transportation and https://www.bostonglobe.com/metro/new-england/massachusetts/cambridge-somerville took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 102 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Orca icon width and height props require a number or use CSS for styling.”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Requests the notification permission on page load
Requests the notification permission on page load.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
7 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 2,592 words of copy
The homepage carries about 2,592 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SUBSCRIBE NOW Starting at $1”.
3 calls to action
The homepage has 3 calls to action, for example “Subscribe Now”, “Sign Up” and “Order Back Issues”.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel and LinkedIn Insight.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Amazon Ads, Comscore, LinkedIn Insight, Meta Pixel and The Trade Desk (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.
25 cookies set on arrival
25Opening the homepage sets 25 cookies, 1 of them by other companies (measured from a US location before any click).
32 other companies contacted
Loading the homepage contacts 32 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 bostonglobe.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on bostonglobe.com, including 19 speed issues, 2 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.