Website review, no card needed
scienceblog.com website review
Visit site (opens in a new tab)Reviewed 11 October 202618 issues · 76 checks
This review found 18 issues worth fixing on scienceblog.com, 4 of them high impact, across 76 checks. The most urgent: render-blocking requests. 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
94AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.7 s |
| Apr 25, 2026 | 1.5 s |
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 935 ms |
| May 16, 2026 | 933 ms |
| May 23, 2026 | 936 ms |
| May 30, 2026 | 940 ms |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 870 ms |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 974 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 90 ms |
| Apr 25, 2026 | 92 ms |
| May 2, 2026 | 87 ms |
| May 9, 2026 | 77 ms |
| May 16, 2026 | 77 ms |
| May 23, 2026 | 75 ms |
| May 30, 2026 | 71 ms |
| Jun 6, 2026 | 72 ms |
| Jun 13, 2026 | 74 ms |
| Jun 20, 2026 | 76 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 78 ms |
| Jul 18, 2026 | 89 ms |
| Jul 25, 2026 | 91 ms |
| Aug 1, 2026 | 91 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 101 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 100 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 141 ms |
| Sep 19, 2026 | 150 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 160 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.4 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Improve image delivery
250 ms · 1.8 MB16 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Mobile performance score: 89
89/100Your mobile performance score is 89 (desktop: 88). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
307 KiBAbout 307 KiB of JavaScript is downloaded but never used on this page.
Taboola adds 109 ms
109 msTaboola costs a phone 109 ms of main-thread work and 363 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Taboola and Cloudflare and others), adding 668 KiB and 233 ms of main-thread time.
Legacy JavaScript
100 ms · 25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Use efficient cache lifetimes
100 ms · 23 KiB4 files are served with short cache lifetimes, so returning visitors download them again (23 KiB).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.
Reduce unused CSS
10 KiBAbout 10 KiB of CSS is downloaded but never applied on this page.
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
4 KiB4 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 237 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Tap response (INP) got 73% slower for real visitors
+73%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 90 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 6.8 s
6.8 sThe page becomes fully interactive after 6.8 s. Good is under 3.8 s.
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
10 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: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 78 ms
78 msReal visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 395 ms
395 msReal visitors wait 395 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 39% faster for real visitors
-39%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.0 s
3.0 sVisually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 39 ms
39 msScripts block the page for only 39 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.6 MB in 47 requests
2.6 MBYour homepage downloads 2.6 MB in 47 requests on a phone: images 1.9 MB (20), scripts 564 KiB (11) and fonts 105 KiB (4). Under 2 MB keeps phones on slow connections fast.
7 images in older formats
7 images (527 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
3 images far larger than shown
240 KiB3 images are downloaded at several times the size a phone draws them, for example brush-teeth-608x421.png at 608 px wide, shown at 112 px. Resized copies would save about 240 KiB.
About 0.7 g of CO₂ per visit
0.73 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.73 g of CO₂e: 87.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 39 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 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
80 internal links, 0 external
The homepage links to 80 pages on scienceblog.com and 0 external pages.
7 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Clear, evidence-led reporting across health, biology, Earth, technology, physics, space and the social sciences. Publis…”.
One H1 headline
Your main headline reads: “Maine lobster traps wash up 3,000 km away in Azores after decades at sea”.
Title: 47 characters
Your title is a healthy 47 characters: “Science Blog | Clear Science for Curious People”.
Canonical URL set
The canonical URL is https://scienceblog.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://scienceblog.com/sitemap_index.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,215 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://scienceblog.com/llms.txt (6 KiB, 18 links), a plain-text guide to the site for AI tools.
Other pages
11 pages without a meta description
https://scienceblog.com/newsletter, https://scienceblog.com/category/health-med, https://scienceblog.com/category/brain-behave, https://scienceblog.com/category/techengineering, https://scienceblog.com/category/earth-energy-environment and https://scienceblog.com/category/lifenonhumans and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page with very little text
https://scienceblog.com/newsletter 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 54 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
25 of 26 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 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 924 words of copy
The homepage carries about 924 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SUBSCRIBE”.
3 calls to action
The homepage has 3 calls to action, for example “Subscribe” and “Contact”.
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics, Plausible and Cloudflare Web Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Taboola (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 scienceblog.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Analytics
- Google Analytics | Plausible
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on scienceblog.com, including 10 speed 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.