SEO report for www.letspushplugin.com
https://www.letspushplugin.com/ · checked Thu, 05 Nov 2026 01:19 GMT
Fix these first
- H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
On WordPress: Most themes show the page title as the H1. In the editor, make sure no other block uses Heading 1 – use Heading 2 for sections.
- Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- Render-blocking resourceshigh
2 blocking script(s) and 7 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- HTTP → HTTPS redirecthigh
http:// does not redirect to https://.
Fix: 301-redirect all http:// requests to https://.
- Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- Trust pages (E-E-A-T)medium
Links found to contact; missing about and privacy.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
- Imagesmedium
9 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
On WordPress: Install a free image optimiser plugin (such as EWWW Image Optimizer or Smush) to shrink images and serve WebP.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to letspushplugin.com…
Indexing & crawling 100%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap index found at https://www.letspushplugin.com/sitemap_index.xml listing 10 sitemaps.
Declared in robots.txt.
Most recent lastmod: 2026-11-05T01:17:55+00:00.
- ✓
Canonical URLhigh
Canonical: https://www.letspushplugin.com/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://letspushplugin.com/ → https://www.letspushplugin.com/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
letspushplugin.com redirects to www.letspushplugin.com.
Search snippet & sharing 71%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“Letspush - Web Push Notifications”
About 306px of Google's ~580px desktop width.
- !
Meta descriptionhigh
71 characters, ~487px of ~990px.
Short – sell the click with a benefit and a call to action.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the meta description.
- ✗
Faviconlow
No favicon linked.
Fix: Add a square favicon at least 48×48px.
On WordPress: Appearance → Customize → Site Identity → Site Icon (Settings → General in newer versions).
- ✓
Languagelow
lang="en-US"
Content quality 60%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
489 words of main content (menus and footer excluded).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- ✓
Readabilitymedium
Flesch reading ease 56 (fairly easy), about 16 words per sentence.
- ✓
Topic focushigh
4 of 4 title keywords appear in the main content.
- ✗
H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
On WordPress: Most themes show the page title as the H1. In the editor, make sure no other block uses Heading 1 – use Heading 2 for sections.
- ✓
Heading structuremedium
10 headings for 489 words.
Levels are in order.
- ✗
Text-to-code ratiolow
3% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 38%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✗
Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✗
Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✗
Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- ✗
Trust pages (E-E-A-T)medium
Links found to contact; missing about and privacy.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
1 JSON-LD block(s): CollectionPage, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 100%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
8 internal and 2 external links.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- ✓
Broken links (sample)high
Checked 1 internal link(s).
No broken links found.
Performance 43%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- !
Server response (TTFB)high
1363 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.
- ✓
HTML sizemedium
116 kB of HTML.
- ✓
Compressionmedium
Compressed with br.
- ✗
Render-blocking resourceshigh
2 blocking script(s) and 7 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- !
Scripts & third partiesmedium
25 script tag(s); files loaded from 1 other domain(s): fonts.googleapis.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
9 image(s).
9 without width/height – can cause layout shift (CLS).
6 image(s) after the first three aren't lazy-loaded.
0 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
On WordPress: Install a free image optimiser plugin (such as EWWW Image Optimizer or Smush) to shrink images and serve WebP.
- ✗
Cachinglow
No Cache-Control header.
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
Security 50%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✗
HTTP → HTTPS redirecthigh
http:// does not redirect to https://.
Fix: 301-redirect all http:// requests to https://.
- ✗
HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- ✗
Security headerslow
Present: none.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 80%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✓
Image alt textmedium
All 9 images have alt text.
- ✓
Link nameslow
Every link has a readable name.
- ✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Local SEO not scored
This site doesn't look like a local business, so these checks are shown for information and not scored.
- i
LocalBusiness markuphigh
No LocalBusiness structured data.
- i
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
- i
Map & directionslow
No map or directions link.