5.8 sec in total
2.2 sec
3.4 sec
156 ms
Welcome to postmedia.com homepage info - get ready to check Postmedia best content for Canada right away, or after learning these important things about postmedia.com
Keeping Canadians in the know with ambitious, trusted and high-quality journalism. Delivering high-value and data-driven marketing solutions to businesses and advertisers.
Visit postmedia.comWe analyzed Postmedia.com page load time and found that the first response time was 2.2 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
postmedia.com performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value18.0 s
0/100
25%
Value4.9 s
65/100
10%
Value230 ms
87/100
30%
Value0.545
13/100
15%
Value10.4 s
24/100
10%
2192 ms
58 ms
75 ms
31 ms
48 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 90% of them (53 requests) were addressed to the original Postmedia.com, 3% (2 requests) were made to Stats.wordpress.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Postmedia.com.
Page size can be reduced by 373.2 kB (43%)
865.3 kB
492.1 kB
In fact, the total size of Postmedia.com main page is 865.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 574.3 kB which makes up the majority of the site volume.
Potential reduce by 28.0 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 28.0 kB or 74% of the original size.
Potential reduce by 161.9 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Postmedia needs image optimization as it can save up to 161.9 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 118.1 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 118.1 kB or 69% of the original size.
Potential reduce by 65.2 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Postmedia.com needs all CSS files to be minified and compressed as it can save up to 65.2 kB or 80% of the original size.
Number of requests can be reduced by 28 (50%)
56
28
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Postmedia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.postmedia.com
2192 ms
screen.css
58 ms
style.css
75 ms
jquery.min.js
31 ms
jquery.cycle.all.js
48 ms
swfobject.js
84 ms
common.js
73 ms
font-awesome.min.css
88 ms
shortcodes.css
101 ms
dualslider.css
109 ms
style.css
140 ms
jquery.js
214 ms
jquery-migrate.min.js
146 ms
dualslider.js
147 ms
script.js
150 ms
audio-player.js
184 ms
styles.css
183 ms
jquery.cycle.all.js
65 ms
shortcodes.js
152 ms
e-201609.js
6 ms
e-201609.js
30 ms
wp-emoji-release.min.js
69 ms
g.gif
101 ms
bg-shadow.png
28 ms
sm-sprite.png
56 ms
search-btn.png
61 ms
search-field.png
57 ms
pmn-logo-new.jpg
112 ms
nav-gradient.png
61 ms
sliderNav.gif
78 ms
Postmedia-Network-Slide-logo.jpg
179 ms
Postmedia-Network-Inc-2_03-logo1.png
180 ms
slideNationalPost_03-logo.png
182 ms
slideVancouverSun-logo.png
165 ms
slideCalgaryherald-logo.png
207 ms
EJ_Masthead_RGB-tm.png
213 ms
LP_RGB_Pillbox-slide.png
263 ms
SP_Masthead_RGB-slide.png
274 ms
slideOttawaCitizen-logo.png
305 ms
WS_RGB_Pillbox.png
282 ms
slideTheGazette-logo.png
353 ms
sliderInfoMart-logo.png
311 ms
slideCanadaCom-logo.png
387 ms
Sun-main-logo-sm.jpg
457 ms
24HOURS-LOGO-toronto.png
394 ms
vancouver_24hrs-no-background.png
406 ms
LFP-sm.jpg
438 ms
canoe1.jpg
433 ms
content-top-line.png
436 ms
dotted-line.png
444 ms
style.css
460 ms
pmn-footer.png
488 ms
solid-line.png
487 ms
clanot-news-webfont.woff
537 ms
clanot-book-webfont.woff
548 ms
clanot-medium-webfont.woff
555 ms
print.css
51 ms
shortcodes-tablet.css
54 ms
shortcodes-mobile.css
52 ms
postmedia.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
postmedia.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
postmedia.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Postmedia.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Postmedia.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
postmedia.com
Open Graph description is not detected on the main page of Postmedia. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: