2.9 sec in total
473 ms
2.1 sec
330 ms
Visit epaper.ottawacitizen.com now to see the best up-to-date Epaper Ottawa Citizen content for Canada and also check out these interesting facts you probably never knew about epaper.ottawacitizen.com
Visit epaper.ottawacitizen.comWe analyzed Epaper.ottawacitizen.com page load time and found that the first response time was 473 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
epaper.ottawacitizen.com performance score
name
value
score
weighting
Value5.8 s
5/100
10%
Value14.8 s
0/100
25%
Value10.2 s
8/100
10%
Value1,560 ms
13/100
30%
Value0.332
34/100
15%
Value13.9 s
10/100
10%
473 ms
9 ms
13 ms
54 ms
53 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 10% of them (9 requests) were addressed to the original Epaper.ottawacitizen.com, 60% (56 requests) were made to Cache-res.pressdisplay.com and 11% (10 requests) were made to Cache3-img1.pressdisplay.com. The less responsive or slowest element that took the longest time to load (668 ms) relates to the external source Cache-res.pressdisplay.com.
Page size can be reduced by 190.3 kB (19%)
1.0 MB
837.3 kB
In fact, the total size of Epaper.ottawacitizen.com main page is 1.0 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. 60% of websites need less resources to load. Images take 839.2 kB which makes up the majority of the site volume.
Potential reduce by 44.5 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 44.5 kB or 79% of the original size.
Potential reduce by 68.3 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. Epaper Ottawa Citizen images are well optimized though.
Potential reduce by 70.5 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 70.5 kB or 57% of the original size.
Potential reduce by 7.1 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. Epaper.ottawacitizen.com needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 77% of the original size.
Number of requests can be reduced by 50 (57%)
87
37
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epaper Ottawa Citizen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
viewer.aspx
473 ms
sso.js
9 ms
capture_client.js
13 ms
WebResource.ashx
54 ms
WebResource.ashx
53 ms
WebResource.ashx
52 ms
WebResource.ashx
46 ms
WebResource.ashx
75 ms
server.html
96 ms
ResourceManagerHandler.ashx
85 ms
jstemplates.ashx
82 ms
se_ottawacitizen_sitecover_bg.gif
64 ms
logo.gif
63 ms
logo-1.gif
62 ms
sitecover_tab.gif
62 ms
1x1.gif
66 ms
toolb_tab_bg.gif
64 ms
se_canwest_cc_logo.gif
64 ms
toolb_div_art2.gif
66 ms
ext-ottawacitizen-pd-theme.gif
66 ms
toolb_but_help.gif
85 ms
toolb_but_arrow.gif
88 ms
toolb_but_services.gif
89 ms
toolb_but_login.gif
88 ms
HomePageRedir.aspx
82 ms
cookiesstorage.aspx
154 ms
account_digitalpapers_s_code.js
7 ms
global_s_code.js
9 ms
local_digitalpapers_s_code.js
8 ms
ga.js
6 ms
json.js
346 ms
member.js
398 ms
member.css
369 ms
i_tri_down.gif
75 ms
pan_tab_bg.gif
73 ms
pan_tab2.gif
77 ms
pan_tab2_g.gif
83 ms
pan_tab_hide.gif
95 ms
pan_tab_show.gif
87 ms
pan_tab3.gif
89 ms
pan_tab3_g.gif
86 ms
but_thumbs.gif
99 ms
but_addbookmark.gif
107 ms
bbar_bg.gif
114 ms
tbar_div.gif
113 ms
json2-min.js
66 ms
__utm.gif
31 ms
firstevent
23 ms
s13427527768071
11 ms
homepage_v2.aspx
102 ms
WebResource.ashx
29 ms
%7BImageDir%7D1x1.gif
76 ms
getimage.aspx
388 ms
s11370049824472
16 ms
event
111 ms
wait-loading.gif
179 ms
shadow-large.png
112 ms
se_ottawacitizen_hd_logo.png
310 ms
se_ottawacitizen_hd_btn.png
280 ms
se-itunes_oc_960x300.jpg
546 ms
se_ottawacitizen_div1.png
188 ms
se_ottawacitizen_viewtoday.png
425 ms
se_ottawacitizen_button-1.png
306 ms
se_ottawacitizen_button-2.png
332 ms
se_ottawacitizen_button-3.png
402 ms
se_ottawacitizen_tbg.png
407 ms
se_ottawacitizen_div2.png
492 ms
se_ottawacitizen_prctb.png
532 ms
se_ottawacitizen_div3.png
541 ms
se_ottawacitizen_feature.png
607 ms
se_ottawacitizen_arr.png
544 ms
se_ottawacitizen_div-v.png
598 ms
se_ottawacitizen_dbg.png
646 ms
se_ottawacitizen_ft-logo.png
668 ms
p_x.gif
574 ms
getimage.aspx
331 ms
getimage.aspx
352 ms
getimage.aspx
334 ms
getimage.aspx
398 ms
getimage.aspx
330 ms
getimage.aspx
562 ms
getimage.aspx
642 ms
getimage.aspx
644 ms
getimage.aspx
663 ms
HomePageHandler.ashx
80 ms
webresource.ashx
192 ms
GetCatalog.ashx
406 ms
UserSettingsHandler.ashx
84 ms
HomePageHandler.ashx
78 ms
__utm.gif
4 ms
ticker_pause.gif
280 ms
ticker_pause.gif
283 ms
dest4.html
28 ms
epaper.ottawacitizen.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
epaper.ottawacitizen.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
Missing source maps for large first-party JavaScript
epaper.ottawacitizen.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Epaper.ottawacitizen.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 Epaper.ottawacitizen.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.
epaper.ottawacitizen.com
Open Graph description is not detected on the main page of Epaper Ottawa Citizen. 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: