Website review, no card needed
savetheworldeveryday.com website review
Visit site (opens in a new tab)Reviewed 17 November 202634 issues · 72 checks
This review found 34 issues worth fixing on savetheworldeveryday.com, 9 of them high impact, across 72 checks. The most urgent: use efficient cache lifetimes. 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
75CClosest competitors among reviewed websites
Compare side by sideOne 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
Use efficient cache lifetimes
1.1 s · 1.6 MB48 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
Render-blocking requests
2.1 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Improve image delivery
1.6 MB11 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 74
74/100Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 90 KiBAbout 90 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
600 ms · 80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, mailerlite.com and Google Fonts and others), adding 177 KiB and 160 ms of main-thread time.
Minify CSS
150 ms · 4 KiB4 KiB could be saved by minifying CSS.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 106 ms. During a long task the page ignores taps.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 210 ms of it running JavaScript. That is comfortably low.
Server response: 99 ms
99 msYour server sent the HTML in 99 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.5 s
5.5 sYour largest element takes 5.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: 7.0 s
7.0 sThe page becomes fully interactive after 7.0 s. Good is under 3.8 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 40 ms
40 msScripts block the page for only 40 ms while loading. Good is under 200 ms.
Images and page weight
2 images over 500 KB
2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.
Page weight: 2.7 MB in 55 requests
2.7 MBYour homepage downloads 2.7 MB in 55 requests on a phone: images 2.1 MB (12), scripts 277 KiB (13) and stylesheets 120 KiB (24). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (2.0 MB) 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.
8 images below the first screen load straight away
8 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 90.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
57 text elements with low contrast
57 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 1 more 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.
Title is long (81 characters)
Your title is 81 characters, so Google will cut it off around 60: “- Making choices to put back together a world that feels like it's falling apart.”.
No social preview image
No Open Graph image (also missing: og:title), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.savetheworldeveryday.com/sitemap_index.xml, so Google discovers your pages only by following links.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
77 internal links, 0 external
The homepage links to 77 pages on savetheworldeveryday.com and 0 external pages.
4 checks passed
Meta description: 79 characters
Your meta description is 79 characters: “Making choices to put back together a world that feels like it's falling apart.”.
Canonical URL set
The canonical URL is https://www.savetheworldeveryday.com/.
Structured data in place
Structured data found: BreadcrumbList, CollectionPage, Organization and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No llms.txt
There is no https://www.savetheworldeveryday.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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (899 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.savetheworldeveryday.com/author/wandaboker declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.savetheworldeveryday.com/author/wandaboker all use the title “- Making choices to put back together a world that feels like it's fa…”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://www.savetheworldeveryday.com/contact, https://www.savetheworldeveryday.com/category/clean-eating-clean-cooking, https://www.savetheworldeveryday.com/category/sustainable-shopping, https://www.savetheworldeveryday.com/category/action-for-change, https://www.savetheworldeveryday.com/category/podcasts and https://www.savetheworldeveryday.com/category/living-plastic-free and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.savetheworldeveryday.com/home-about, https://www.savetheworldeveryday.com/contact and https://www.savetheworldeveryday.com/author/wandaboker have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.savetheworldeveryday.com/action-for-change/wear-it-repair-it-wear-it-repeat, https://www.savetheworldeveryday.com/action-for-change/we-put-solar-panels-on-our-roof-let-me-debunk-3-myths-about-going-solar and https://www.savetheworldeveryday.com/action-for-change/its-plastic-free-july-take-the-plastic-free-challenge took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
19 small tap targets
19 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 887 words of copy
The homepage carries about 887 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
6 other companies contacted
Loading the homepage contacts 6 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 savetheworldeveryday.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
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Oracle Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on savetheworldeveryday.com, including 11 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.