2.7 sec in total
87 ms
1.8 sec
845 ms
Welcome to wpmedia.edmontonjournal.com homepage info - get ready to check Wpmedia Edmonton Journal best content for Canada right away, or after learning these important things about wpmedia.edmontonjournal.com
Read latest breaking news, updates, and headlines. Edmonton Journal offers information on latest national and international events & more.
Visit wpmedia.edmontonjournal.comWe analyzed Wpmedia.edmontonjournal.com page load time and found that the first response time was 87 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
wpmedia.edmontonjournal.com performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value32.3 s
0/100
25%
Value10.7 s
7/100
10%
Value4,150 ms
1/100
30%
Value0.019
100/100
15%
Value32.2 s
0/100
10%
87 ms
9 ms
140 ms
19 ms
26 ms
Our browser made a total of 177 requests to load all elements on the main page. We found that 20% of them (35 requests) were addressed to the original Wpmedia.edmontonjournal.com, 12% (21 requests) were made to App.canada.com and 8% (15 requests) were made to S1.wp.com. The less responsive or slowest element that took the longest time to load (511 ms) relates to the external source App.canada.com.
Page size can be reduced by 1.9 MB (57%)
3.4 MB
1.4 MB
In fact, the total size of Wpmedia.edmontonjournal.com main page is 3.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 211.2 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 211.2 kB or 79% of the original size.
Potential reduce by 11.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. Wpmedia Edmonton Journal images are well optimized though.
Potential reduce by 1.7 MB
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 1.7 MB or 67% of the original size.
Potential reduce by 22.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. Wpmedia.edmontonjournal.com needs all CSS files to be minified and compressed as it can save up to 22.2 kB or 89% of the original size.
Number of requests can be reduced by 69 (46%)
151
82
The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wpmedia Edmonton Journal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 58 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
wpmedia.edmontonjournal.com
87 ms
postmediaedmontonjournal2.wordpress.com
9 ms
edmontonjournal.com
140 ms
19 ms
26 ms
polarAd-2.0-prod.js
230 ms
VisitorAPI.js
119 ms
core.js
125 ms
pm-omniture.js
100 ms
zephyr.js
39 ms
18 ms
29 ms
widgets.js
32 ms
28 ms
lsa-dynamic.js
97 ms
w.js
35 ms
conversion.js
96 ms
plugin.js
224 ms
gpt.js
81 ms
id
78 ms
ej_300x300_rgb.png
104 ms
postmedia.png
53 ms
mayes_lowres_03-18-16.jpeg
80 ms
arrow.png
55 ms
11796867.jpg
78 ms
pacifica1.jpg
78 ms
next.jpg
51 ms
11789116.jpg
77 ms
play-button-overlay.png
53 ms
logo-postmedia.png
72 ms
previous.jpg
50 ms
uploaded-by-mark-morris-email-mmorrisincentre-net1.jpeg
168 ms
calgary-herald3.jpeg
169 ms
uploaded-by-roger-levesque-email-textureshaw-ca-ph3.jpeg
169 ms
edmonton-ab-jessica-pott-holds-her-son-henry-in-the-stoll.jpeg
168 ms
edmonton-ab-march-19-2016-the-city-of-edmonton-hosted.jpeg
167 ms
hundreds-of-truckers-rallied-in-fort-st-john-and-two-other.jpeg
168 ms
vancouver-canucks-v-edmonton-oilers1.jpeg
249 ms
11795205.jpg
260 ms
edmonton-alta-march-19-2016-stephen-badry-skips-throu.jpeg
250 ms
edmonton-police-service-eps-cst-nathalie-perrault-right.jpeg
247 ms
edmonton-ab-dave-eggen-minister-of-health-jade-slyk.jpeg
249 ms
11586933.jpg
258 ms
edmonton-alberta-july-15-2011-edmonton-police-service-c.jpeg
252 ms
11795130.jpg
250 ms
no-iptc-info-found17.jpeg
251 ms
uploaded-by-elise-stolte-email-estolteedmontonjournal14.jpeg
252 ms
edmonton-alta-march-15-2016-labour-minister-christina.jpeg
253 ms
official-opposition-releases-wildrose-jobs-action-plan.jpeg
255 ms
11607101.jpg
253 ms
shots-of-thom-yorke-of-british-band-radiohead.jpeg
254 ms
celebrity-juno-winning-chef-roger-mooking-unveils-his-juno.jpeg
257 ms
edmonton-ab-march-12-2016-from-left-laura-vey-allyse.jpeg
257 ms
night-of-the-living-dead.jpeg
258 ms
the-smalls-reunite-to-play-the-last-day-of-sonic-boom-2014.jpeg
259 ms
11793919.jpg
339 ms
uploaded-by-keri-sweetman-email-ksweetmanedmontonjourn.jpeg
340 ms
11796792.jpg
259 ms
11794629.jpg
322 ms
11794572.jpg
323 ms
sprucegrovesaints1.jpg
325 ms
11794603.jpg
326 ms
photo-uploaded-thursday-june-5-2014-conceptual-images-of1.jpeg
326 ms
edmonton-ab-kaley-and-her-son-trystan-braemer-school-fo1.jpeg
327 ms
nydebuts.jpg
69 ms
11794093.jpg
124 ms
11791389.jpg
123 ms
online_classifieds-140x80.png
162 ms
workopolis-border-140x80.png
163 ms
flyercity_ca-border-140x80.png
162 ms
remembering_ca-border-140x80.png
164 ms
celebrating_com-border-140x80.png
165 ms
uber-1.jpg
121 ms
BentonSans-Regular.otf
27 ms
BentonSans-Bold.otf
26 ms
fef1fa78-f7d7-414c-8350-a1dc2527200b-3.woff
117 ms
7adca158-48f5-4b45-af57-5441f63718c6-3.woff
117 ms
glyphicons-regular.woff
121 ms
5993ebd0-66f0-45c7-8230-d8c123bfc3a7-3.woff
115 ms
pubads_impl_82.js
119 ms
id
109 ms
229 ms
BentonSans-Medium.otf
52 ms
312 ms
TitlingGothicFBCond-Regular.otf
37 ms
203 ms
296 ms
285 ms
container.html
59 ms
105 ms
advertisement.js
7 ms
pmvids-player.css
8 ms
pmvids-error-config.js
11 ms
pmvids-utils.js
5 ms
511 ms
social-sprite.png
3 ms
pmvids-ad-controller.js
7 ms
admin-ajax.php
142 ms
traffic_map_3.jpg
6 ms
pmvids-analytics-controller.js
31 ms
sidebar.php
186 ms
pmvids-video-controller.js
6 ms
wrapper.js
455 ms
widgets.js
9 ms
86b871a8-3c21-46cd-a9e2-4876f7d6b9c1-3.woff
58 ms
admin-ajax.php
383 ms
pp4.js
29 ms
pmvids-video.js
21 ms
hp_w_ih_l.svg
35 ms
pmvids-video-ui.js
35 ms
ga.js
239 ms
beacon.js
240 ms
282 ms
css
279 ms
sidebar.css
272 ms
jquery-1.11.1.min.js
278 ms
jwplayer.js
275 ms
streamsense.min.js
270 ms
s2nComScore20140609.js
274 ms
ads
376 ms
event
213 ms
wt
177 ms
ads
225 ms
wt
169 ms
ads
217 ms
wt
163 ms
ads
217 ms
wt
158 ms
ads
205 ms
wt
153 ms
ads
200 ms
g.gif
65 ms
pmvids-playlist-controller.js
63 ms
__utm.gif
103 ms
g.gif
92 ms
g.gif
95 ms
s06482569640502
95 ms
154 ms
analytics.js
68 ms
th_Qx3OjTxrQh400px-Dallas_Mavericks_logo-UP.jpg
71 ms
rtpdjh4x8dub9totr6f95luuk6lsup56.jpg
123 ms
1-530pq9psn8s3n07976srpn98q4n68283.jpg
67 ms
u5ok3rhrsb6hf32z15nrh7vwpbhw9zxj.jpg
64 ms
hzm7e0ddqi8c6xai4yztov0d7k7tyrc2.jpg
118 ms
nvktv7wz3aqta1stsqixapdn4iqzpqd2.jpg
64 ms
i3kg2oy1w7tbquenrygwfc4kq5bpeq2w.jpg
63 ms
ejxywwfhxgo1y1oh0ab6drzvexlrhy3y.jpg
65 ms
d3e6senqc4dyhbgkvg7n2fyf6vg2agnq.jpg
107 ms
9n18si6d31feaq0tdy15jeeqqi2hvnr2.jpg
65 ms
1-019082347on5s999084o646p83s75pps.jpg
117 ms
ajax-loader.gif
56 ms
sidebarGradientTop.png
58 ms
sidebarGradientBot.png
58 ms
LiveRail.AdManager.JWPlayer-6.8.1.plugin.js
92 ms
gapro.js
98 ms
pmvids-playlist-ui.js
73 ms
uparrow.png
72 ms
downarrow.png
73 ms
close_black.png
115 ms
338
248 ms
nometer.json
92 ms
collect
135 ms
0XxGQsSc1g4rdRdjJKZrNBsxEYwM7FgeyaSgU71cLG0.woff
58 ms
LKf8nhXsWg5ybwEGXk8UBQ.woff
89 ms
collect
73 ms
wt
33 ms
wt
58 ms
wt
55 ms
wt
51 ms
wt
52 ms
ads
62 ms
pmvids-social-share-controller.js
31 ms
container.html
25 ms
handshake.html
26 ms
pmvids-social-share-ui.js
3 ms
lib-bc-player.js
16 ms
bcc_postmedia_adobe_analytics-0.1.0.js
46 ms
wpmedia.edmontonjournal.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
wpmedia.edmontonjournal.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
wpmedia.edmontonjournal.com SEO score
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
Tap targets are not sized appropriately
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wpmedia.edmontonjournal.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wpmedia.edmontonjournal.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.
wpmedia.edmontonjournal.com
Open Graph description is not detected on the main page of Wpmedia Edmonton Journal. 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: