3.8 sec in total
181 ms
3 sec
630 ms
Welcome to digital.windsorstar.com homepage info - get ready to check Digital Windsor Star best content for Canada right away, or after learning these important things about digital.windsorstar.com
Visit digital.windsorstar.comWe analyzed Digital.windsorstar.com page load time and found that the first response time was 181 ms 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.
digital.windsorstar.com performance score
name
value
score
weighting
Value6.4 s
3/100
10%
Value16.3 s
0/100
25%
Value10.7 s
7/100
10%
Value2,670 ms
4/100
30%
Value0.342
33/100
15%
Value16.6 s
6/100
10%
181 ms
15 ms
29 ms
131 ms
103 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Digital.windsorstar.com, 11% (10 requests) were made to Cache3-img1.pressdisplay.com and 9% (8 requests) were made to Epaper.windsorstar.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Canada.com.
Page size can be reduced by 240.5 kB (23%)
1.1 MB
826.7 kB
In fact, the total size of Digital.windsorstar.com main page is 1.1 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. 75% 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. Images take 878.9 kB which makes up the majority of the site volume.
Potential reduce by 44.4 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.4 kB or 79% of the original size.
Potential reduce by 118.6 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, Digital Windsor Star needs image optimization as it can save up to 118.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
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. Digital.windsorstar.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 47 (56%)
84
37
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Digital Windsor Star. 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
181 ms
sso.js
15 ms
capture_client.js
29 ms
WebResource.ashx
131 ms
WebResource.ashx
103 ms
WebResource.ashx
100 ms
WebResource.ashx
100 ms
WebResource.ashx
99 ms
server.html
608 ms
account_digitalpapers_s_code.js
1416 ms
global_s_code.js
561 ms
local_digitalpapers_s_code.js
561 ms
ga.js
48 ms
json.js
801 ms
member.js
800 ms
member.css
559 ms
ResourceManagerHandler.ashx
265 ms
jstemplates.ashx
263 ms
logo.gif
150 ms
logo-1.gif
148 ms
1x1.gif
150 ms
se_canwest_cc_logo.gif
333 ms
toolb_div_art2.gif
332 ms
toolb_but_help.gif
332 ms
toolb_but_arrow.gif
359 ms
toolb_but_services.gif
360 ms
toolb_but_login.gif
351 ms
i_tri_down.gif
358 ms
but_thumbs.gif
359 ms
but_addbookmark.gif
357 ms
tbar_div.gif
377 ms
se_windsorstar_sitecover_bg.gif
346 ms
sitecover_tab.gif
334 ms
toolb_tab_bg.gif
397 ms
ext-windsorstar-pd-theme.gif
344 ms
json2-min.js
341 ms
pan_tab_bg.gif
145 ms
pan_tab2.gif
106 ms
pan_tab2_g.gif
74 ms
pan_tab_hide.gif
83 ms
pan_tab_show.gif
75 ms
pan_tab3.gif
71 ms
pan_tab3_g.gif
76 ms
bbar_bg.gif
73 ms
HomePageRedir.aspx
89 ms
cookiesstorage.aspx
168 ms
homepage_v2.aspx
119 ms
WebResource.ashx
9 ms
wait-loading.gif
256 ms
%7BImageDir%7D1x1.gif
224 ms
getimage.aspx
210 ms
shadow-large.png
235 ms
se_windsorstar_hd_logo.png
142 ms
se_windsorstar_hd_btn.png
191 ms
se-itunes_ws_960x300.jpg
144 ms
se_windsorstar_div1.png
145 ms
se_windsorstar_viewtoday.png
190 ms
se_windsorstar_button-1.png
188 ms
se_windsorstar_button-2.png
179 ms
se_windsorstar_button-3.png
306 ms
se_windsorstar_tbg.png
204 ms
se_windsorstar_div2.png
160 ms
se_windsorstar_prctb.png
176 ms
se_windsorstar_div3.png
175 ms
se_windsorstar_feature.png
176 ms
se_windsorstar_arr.png
178 ms
se_windsorstar_div-v.png
175 ms
se_windsorstar_dbg.png
175 ms
se_windsorstar_ft-logo.png
259 ms
p_x.gif
177 ms
getimage.aspx
84 ms
getimage.aspx
83 ms
getimage.aspx
108 ms
getimage.aspx
108 ms
getimage.aspx
108 ms
getimage.aspx
108 ms
getimage.aspx
107 ms
getimage.aspx
107 ms
getimage.aspx
95 ms
HomePageHandler.ashx
121 ms
webresource.ashx
93 ms
firstevent
57 ms
s36651376283261
58 ms
event
35 ms
__utm.gif
39 ms
s33968580046202
31 ms
UserSettingsHandler.ashx
87 ms
dest4.html
47 ms
GetCatalog.ashx
66 ms
digital.windsorstar.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
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.
digital.windsorstar.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
Registers an unload listener
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
digital.windsorstar.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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digital.windsorstar.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 Digital.windsorstar.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.
digital.windsorstar.com
Open Graph description is not detected on the main page of Digital Windsor Star. 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: