Website review, no card needed
postmediadistributionsolutions.com website review
Visit site (opens in a new tab)Reviewed 28 October 202634 issues · 77 checks
This review found 34 issues worth fixing on postmediadistributionsolutions.com, 15 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. 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
68DClosest 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
Reduce unused JavaScript
4.7 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.
Use efficient cache lifetimes
1.8 s · 755 KiB41 files are served with short cache lifetimes, so returning visitors download them again (755 KiB).
Render-blocking requests
1.1 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.9 MB and 2.0 s of main-thread time.
Improve image delivery
1.7 MB1 image could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 989 ms
989 msGoogle Tag Manager costs a phone 989 ms of main-thread work and 1.1 MB 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.
Google CDN adds 555 ms
555 msGoogle CDN costs a phone 555 ms of main-thread work and 1.1 MB 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 207 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
1 checks passed
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 11.4 s
11.4 sThe first text or image appears after 11.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 22.3 s
22.3 sYour largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “AdobeStock_1932245911”.
Time to Interactive: 30.3 s
30.3 sThe page becomes fully interactive after 30.3 s. Good is under 3.8 s.
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 710 ms
710 msScripts block taps and scrolling for 710 ms in total while the page loads. Good is under 200 ms.
25 images without width and height
25 images have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.6 MB in 132 requests
5.6 MBYour homepage downloads 5.6 MB in 132 requests on a phone: scripts 3.0 MB (36), images 2.0 MB (38) and other files 400 KiB (40). Under 2 MB keeps phones on slow connections fast.
About 1.6 g of CO₂ per visit
1.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.60 g of CO₂e: 191.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA commands must have an accessible name (2 elements)
ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 14 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
7 internal links, 18 external
The homepage links to 7 pages on postmediadistributionsolutions.com and 18 external pages.
6 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Postmedia Distribution Solutions provides end-to-end retail execution that helps brands move products efficiently from …”.
One H1 headline
Your main headline reads: “Proof Over Promise”.
Title: 39 characters
Your title is a healthy 39 characters: “Postmedia Distribution Solutions - Home”.
Canonical URL set
The canonical URL is https://www.postmediadistributionsolutions.com/en-ca.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.postmediadistributionsolutions.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.postmediadistributionsolutions.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (300 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.postmediadistributionsolutions.com/fr-ca, which answers with an error. Visitors hit a dead end and search engines drop it.
4 pages share 2 titles
https://www.postmediadistributionsolutions.com/en-ca and / all use the title “Postmedia Distribution Solutions - Home”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages share a meta description
https://www.postmediadistributionsolutions.com/ourstory, https://www.postmediadistributionsolutions.com/ourpartners and / use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.postmediadistributionsolutions.com/en-ca. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Every page has a meta description
All 3 pages that loaded have a meta description.
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 3 pages that loaded have a <title>.
Best practices
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
12 of 12 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 324 words of copy
The homepage carries about 324 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: “Get started”.
3 calls to action
The homepage has 3 calls to action, for example “Get started” and “Learn More”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
16 cookies set on arrival
16Opening the homepage sets 16 cookies (measured from a US location before any click).
38 other companies contacted
Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 postmediadistributionsolutions.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
- HubSpot CMS
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- HubSpot
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 postmediadistributionsolutions.com, including 15 speed issues, 3 SEO 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.