SEO report for www.parcel2go.com
https://www.parcel2go.com/ · checked Wed, 04 Nov 2026 22:36 GMT
Fix these first
- Render-blocking resourceshigh
2 blocking script(s) and 1 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- Title tagcritical
“Parcel Delivery & Courier Services | Send a Parcel | Parcel2Go”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- HTML sizemedium
977 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
26 script tag(s); files loaded from 3 other domain(s): images.ctfassets.net, assets.ctfassets.net, consent.cookiebot.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- Imagesmedium
43 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- 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.
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 parcel2go.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 found at https://www.parcel2go.com/sitemap.xml with 1,322 URLs.
Declared in robots.txt.
This page is listed in it.
Most recent lastmod: 2026-11-03T10:29:58.342Z.
- ✓
Canonical URLhigh
Canonical: https://www.parcel2go.com/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://parcel2go.com/ → https://www.parcel2go.com/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
parcel2go.com redirects to www.parcel2go.com.
- ✓
hreflangmedium
3 hreflang link(s).
All language codes are valid.
Search snippet & sharing 71%
How the page looks in Google results and when shared.
- !
Title tagcritical
“Parcel Delivery & Courier Services | Send a Parcel | Parcel2Go”
About 560px of Google's ~580px desktop width.
Repeated words: parcel.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- ✓
Meta descriptionhigh
144 characters, ~908px 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-GB"
Content quality 100%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
4,246 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 62 (plain English), about 18 words per sentence.
- ✓
Topic focushigh
5 of 5 title keywords appear in the main content.
- ✓
H1 headingcritical
“Compare the Cheapest Parcel Delivery Prices*”
- ✓
Heading structuremedium
29 headings for 4246 words.
Levels are in order.
- ✓
Text-to-code ratiolow
18% of the HTML is visible text.
AI search readiness 88%
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
/llms.txt found.
- ✓
Question-led contentmedium
8 heading(s) phrased as questions, e.g. “Sending With Royal Mail?”.
- ✓
Entity clarityhigh
Identified as: Organization.
6 official profile link(s) (sameAs).
- ✗
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 all three: about, contact and privacy.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
1 JSON-LD block(s): WebSite, Action, EntryPoint, Organization, WebPage, FAQPage, Question, Answer.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Google now shows FAQ rich results only for well-known government and health sites, but the markup still helps machines read your Q&As.
Links 88%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
127 internal and 7 external links.
- !
Anchor text qualitymedium
Same text used for different pages: “uk couriers”, “evri”, “uk’s best couriers”.
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.
3 link(s) point to a redirect – link to the final address instead.
Performance 44%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
152 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
977 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 br.
- ✗
Render-blocking resourceshigh
2 blocking script(s) and 1 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
26 script tag(s); files loaded from 3 other domain(s): images.ctfassets.net, assets.ctfassets.net, consent.cookiebot.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
43 image(s).
5 without width/height – can cause layout shift (CLS).
22 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.
- ✓
Cachinglow
Cache-Control: public, max-age=90, s-maxage=300, stale-while-revalidate=90, stale-if-error=300
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
Security 100%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✓
HSTSmedium
HSTS: max-age=15552000; includeSubDomains
- ✓
Security headerslow
Present: CSP, nosniff, Referrer-Policy, Permissions-Policy, clickjacking protection.
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 83%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: initial-scale=1, width=device-width
- ✓
Image alt textmedium
All 43 images have alt text.
- ✓
Form labelsmedium
All 3 form fields are labelled.
- ✓
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 33%
Signals that help you appear in Google Maps and 'near me' searches.
- ✗
LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- ✓
Contact details on pagemedium
No phone number found.
A UK postcode is shown.
- ✗
Map & directionslow
No map or directions link.
Fix: Add a Google Maps directions link so customers can find you.