SEO report for www.parcelpending.com
https://www.parcelpending.com/ · checked Thu, 05 Nov 2026 03:42 GMT
Fix these first
- Canonical URLhigh
No canonical tag.
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- Render-blocking resourceshigh
2 blocking script(s) and 2 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- Readabilitymedium
Flesch reading ease 27 (difficult), about 17 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- Trust pages (E-E-A-T)medium
Links found to about; missing contact 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.
- HTML sizemedium
979 kB of HTML – heavy for phones (we only analysed the first 1 MB).
Fix: Remove inline bloat, base64 images and unused markup.
- Scripts & third partiesmedium
46 script tag(s); files loaded from 6 other domain(s): bugherd.com, widget.trustpilot.com, cdn-ukwest.onetrust.com, googletagmanager.com, cdn.callrail.com, google.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- Imagesmedium
11 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.
- HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
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 parcelpending.com…
Indexing & crawling 88%
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.parcelpending.com/sitemap_index.xml listing 10 sitemaps.
Declared in robots.txt.
Most recent lastmod: 2026-11-04T20:37:38+00:00.
- ✗
Canonical URLhigh
No canonical tag.
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- ✓
Redirectshigh
1 redirect before the page loaded.
https://parcelpending.com/ → https://www.parcelpending.com/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
parcelpending.com redirects to www.parcelpending.com.
Search snippet & sharing 100%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“Global Smart Package Locker Solutions | Parcel Pending”
About 505px of Google's ~580px desktop width.
- ✓
Meta descriptionhigh
134 characters, ~812px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en-usa"
Content quality 80%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
474 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- ✗
Readabilitymedium
Flesch reading ease 27 (difficult), about 17 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- ✓
Topic focushigh
7 of 7 title keywords appear in the main content.
- ✓
H1 headingcritical
“The Global Leader in Smart Package Locker Solutions”
- ✓
Heading structuremedium
6 headings for 474 words.
Levels are in order.
- ✗
Text-to-code ratiolow
0% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 75%
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
1 heading(s) phrased as questions, e.g. “How Parcel Pending Delivers More”.
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
Identified as: Organization.
5 official profile link(s) (sameAs).
- ✓
Freshness signalsmedium
The page shows when it was published or last updated.
- ✗
Trust pages (E-E-A-T)medium
Links found to about; missing contact 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
2 JSON-LD block(s): WebPage, ReadAction, ImageObject, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, Organization, ContactPoint.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 88%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
30 internal and 1 external links.
- !
Anchor text qualitymedium
Same text used for different pages: “united states (english)”, “canada (english)”, “united kingdom/ireland”, “france”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
1 link(s) point to a redirect – link to the final address instead.
Performance 40%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
181 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- ✗
HTML sizemedium
979 kB of HTML – heavy for phones (we only analysed the first 1 MB).
Fix: Remove inline bloat, base64 images and unused markup.
- ✓
Compressionmedium
Compressed with gzip.
- ✗
Render-blocking resourceshigh
2 blocking script(s) and 2 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
46 script tag(s); files loaded from 6 other domain(s): bugherd.com, widget.trustpilot.com, cdn-ukwest.onetrust.com, googletagmanager.com, cdn.callrail.com, google.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
11 image(s).
9 without width/height – can cause layout shift (CLS).
8 image(s) after the first three aren't lazy-loaded.
2 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
Cache-Control: max-age=600, must-revalidate
- 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 67%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects 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
X-Powered-By reveals “WP Engine”.
Fix: Remove X-Powered-By so attackers can't see your software versions.
Mobile & accessibility 80%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1.0
- ✓
Image alt textmedium
All 11 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.