99.4 sec in total
1 sec
88.3 sec
10.1 sec
Click here to check amazing Saskobits content. Otherwise, check out these important facts you probably never knew about saskobits.com
Obituaries from Leader-Post
Visit saskobits.comWe analyzed Saskobits.com page load time and found that the first response time was 1 sec and then it took 98.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
saskobits.com performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value5.5 s
18/100
25%
Value2.9 s
95/100
10%
Value10 ms
100/100
30%
Value0.095
91/100
15%
Value4.2 s
86/100
10%
1041 ms
381 ms
1184 ms
886 ms
1371 ms
Our browser made a total of 280 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Saskobits.com, 7% (20 requests) were made to Us-u.openx.net and 6% (17 requests) were made to A.tribalfusion.com. The less responsive or slowest element that took the longest time to load (12 sec) relates to the external source Facebook.com.
Page size can be reduced by 4.4 MB (67%)
6.5 MB
2.2 MB
In fact, the total size of Saskobits.com main page is 6.5 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. 85% 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 5.0 MB which makes up the majority of the site volume.
Potential reduce by 140.8 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 140.8 kB or 77% of the original size.
Potential reduce by 16.1 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. Saskobits images are well optimized though.
Potential reduce by 3.4 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 3.4 MB or 68% of the original size.
Potential reduce by 817.7 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. Saskobits.com needs all CSS files to be minified and compressed as it can save up to 817.7 kB or 84% of the original size.
Number of requests can be reduced by 196 (77%)
256
60
The browser has sent 256 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saskobits. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 111 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
1041 ms
asr.css
381 ms
glyphicons.css
1184 ms
css
886 ms
css
1371 ms
jquery.min.js
343 ms
jquery.loading.js
2464 ms
1736730124.js
2453 ms
ls-legacy.js
2436 ms
segments.json
2412 ms
css
2412 ms
ClientStorage.ascx.js
1130 ms
ObituaryNavigator.js
1130 ms
jquery-ui-custom.js
1130 ms
outdatedbrowser.js
1129 ms
SiteNavigationV2.ascx.js
2237 ms
LocalSpotlight.ascx.js
2237 ms
RecentObituaries.ascx.js
2221 ms
RecentObituariesV2.ascx.js
1218 ms
SearchObitContent.ascx.js
2236 ms
ResourceModule.ascx.js
2236 ms
Custom11x5Ad.ascx.js
8088 ms
pl.ashx
1099 ms
include.aspx
8144 ms
core.js
7905 ms
event
4953 ms
a1625899514.html
5468 ms
gpt.js
1034 ms
publishertag.js
762 ms
10698.js
1975 ms
rta.js
3104 ms
gtm.js
1689 ms
quant.js
1820 ms
icon_search.png
1339 ms
1451143_20170905.jpgx
1767 ms
spacer.gif
1339 ms
searchbuttonlimited.gif
1337 ms
poweredbylegacy.png
1337 ms
flowers1.gif
1338 ms
flowers2.gif
1303 ms
mapportal.png
1635 ms
footer_arrow.png
1634 ms
1449670_20170905.jpgx
1764 ms
photo_1_4711e13416131194eautu3412145_20170905.jpgx
1765 ms
photo_1_4157e124160050eb49rjt1d53c17_20170905.jpgx
1711 ms
1451065_20170905.jpgx
1709 ms
photo_1_450b10401600511a43uvi365f24e_20170905.jpgx
1709 ms
1451185_20170905.jpgx
2752 ms
1451124_20170905.jpgx
2540 ms
leaderpost.gif
2520 ms
obit_preview.png
2520 ms
ClientStorageProxy.aspx
1474 ms
affiliateartwork.axd
1473 ms
pubads_impl_147.js
4562 ms
canwest_default_variables.js
1111 ms
remembering_variables.js
1546 ms
include.aspx
1681 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
1522 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
1601 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
2746 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
2747 ms
sync
2916 ms
rules-p-57OGVHgSOoedo.js
1915 ms
st.js
1770 ms
analytics.js
1725 ms
khp.js
1665 ms
1664607.js
1664 ms
fbevents.js
2575 ms
embed.js
912 ms
header_footer_phase2.css
808 ms
searchmorearrow.gif
1122 ms
logo-regina.png
1120 ms
legacycomad.axd
793 ms
postmedia.png
796 ms
legacycomad.axd
5961 ms
linkid.js
5637 ms
ads
3366 ms
container.html
3337 ms
ads
3274 ms
ads
3052 ms
1077383918984246
2970 ms
pixel;r=370117754;rf=0;a=p-57OGVHgSOoedo;url=http%3A%2F%2Fwww.legacy.com%2Fobituaries%2Fleaderpost%2F;fpan=1;fpa=P0-2132666824-1504647345038;ns=0;ce=1;cm=;ref=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504647345038;tzo=-180;ogl=site_name.Leader-Post%2Ctype.legacy%3Aspotlight%2Ctitle.Obituary%20News%20-%20Leader-Post%2Curl.http%3A%2F%2Fwww%252Elegacy%252Ecom%2Fobituaries%2Fleaderpost%2F%2Cimage.http%3A%2F%2Fak-static%252Elegacy%252Enet%2Fobituaries%2Fimages%2Fobituary%2Fobituaryportal%2Fobituaryne%2Cdescription.Obituaries%20from%20Leader-Post
2762 ms
bid
1067 ms
trinity.js
1094 ms
cygnus
896 ms
arj
1040 ms
callback=_nw2e.closures.c0
201 ms
pd
342 ms
jpt
652 ms
cfcm.ashx
489 ms
openx
459 ms
pixel
455 ms
sd
255 ms
openx
432 ms
sd
392 ms
bid
420 ms
trinity.js
1012 ms
arj
1331 ms
cygnus
940 ms
sd
842 ms
sd
787 ms
sd
761 ms
ads
1382 ms
headerstats
1241 ms
pd
976 ms
ads
398 ms
ads
330 ms
f59d9edc-e54e-a07b-79e3-444156b5270a
1095 ms
jpt
830 ms
bid
651 ms
trinity.js
3126 ms
cygnus
2831 ms
arj
2525 ms
sd
346 ms
ads
3305 ms
headerstats
2341 ms
pixel
7693 ms
collect
1990 ms
collect
7147 ms
osd_listener.js
9062 ms
osd.js
4023 ms
11956 ms
ad
5629 ms
generic
2471 ms
pd
2353 ms
sync
2353 ms
sync
4643 ms
gpt.js
225 ms
view
0 ms
gpt.js
10963 ms
jpt
4138 ms
bid
4186 ms
arj
4433 ms
trinity.js
4872 ms
cygnus
4140 ms
optimizationscripts.js
3679 ms
affiliateartwork.axd
3464 ms
us.gif
8205 ms
OpenX.ashx
8204 ms
us.gif
8202 ms
ads
7341 ms
headerstats
4728 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
2721 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
2659 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
4475 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
5182 ms
jpt
4895 ms
postmedia_obj_init.js
2228 ms
VisitorAPI.js
2277 ms
7923 ms
header_footer.css
7863 ms
include.aspx
5866 ms
ga-audiences
10934 ms
dds
6685 ms
adj
3707 ms
pd
5044 ms
us.gif
6385 ms
id
8506 ms
us.gif
4575 ms
sd
4204 ms
ads
3425 ms
headerstats
3426 ms
sd
3354 ms
sd
3835 ms
controltag
6295 ms
container.html
2352 ms
ads
4111 ms
5586 ms
cksync.php
3784 ms
sd
2051 ms
sd
2226 ms
id
5848 ms
container.html
2720 ms
ads
2745 ms
logo-postmedia.png
3368 ms
10698.js
2243 ms
osd_listener.js
2175 ms
sd
1698 ms
sd
1045 ms
sd
672 ms
sync
338 ms
firstevent
632 ms
id
2132 ms
sd
3276 ms
RecentObituariesHandler.ashx
2129 ms
ui-bg_inset-hard_100_fcfdfd_1x100.png
1700 ms
getids
1560 ms
x.gif
1109 ms
;ord=1504647376923
1068 ms
x.js
1055 ms
x.gif
1006 ms
;ord=1504647376978
1004 ms
controltag.js.1c86c30cac854ccdacab6e3099f5b9ee
266 ms
r2
660 ms
266156-10.js
604 ms
img;p=11152201592392;idfa=;idfa_lat=;aaid=;aaid_lat=;cache=1589931500
4993 ms
7538598542350745402
1397 ms
abg.js
5119 ms
m_js_controller.js
5118 ms
m_window_focus_non_hydra.js
5118 ms
show_ads.js
1123 ms
x_button_blue2.png
5085 ms
proxy.3d2100fd7107262ecb55ce6847f01fa5.html
4019 ms
zrt_lookup.html
11777 ms
show_ads_impl.js
4452 ms
tags.js
7203 ms
ads
5885 ms
ads
4274 ms
pl
1371 ms
ad
4207 ms
generic
1279 ms
sync
4174 ms
JIvJb9V0.js
3681 ms
us.gif
4045 ms
us.gif
5017 ms
googlelogo_dark_color_84x28dp.png
9148 ms
s
8452 ms
iconx2-000000.png
8487 ms
us.gif
4406 ms
ads
6481 ms
us.gif
1926 ms
tags.js
5272 ms
emily.html
4937 ms
361047.gif
1461 ms
displayAd.js
1419 ms
pixel;r=611723513;labels=Page%20Load.DPID.91939%2CPage%20Load.Site%20Category.1b.DPID.91939%2CPage%20Load.Site%20Category.2d.DPID.91939%2CPage%20Load.Site%20Category.0.DPID.91939%2CPage%20Load.Site%20Category.3b.DPID.91939;event=refresh;rf=3;a=p-573scDfDoUH6o;url=http%3A%2F%2Fwww.legacy.com%2Fobituaries%2Fleaderpost%2F;fpan=0;fpa=P0-2132666824-1504647345038;ns=0;ce=1;cm=;ref=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504647394092;tzo=-180;ogl=site_name.Leader-Post%2Ctype.legacy%3Aspotlight%2Ctitle.Obituary%20News%20-%20Leader-Post%2Curl.http%3A%2F%2Fwww%252Elegacy%252Ecom%2Fobituaries%2Fleaderpost%2F%2Cimage.http%3A%2F%2Fak-static%252Elegacy%252Enet%2Fobituaries%2Fimages%2Fobituary%2Fobituaryportal%2Fobituaryne%2Cdescription.Obituaries%20from%20Leader-Post
2232 ms
rules-p-573scDfDoUH6o.js
2231 ms
j.ad
1503 ms
tag.aspx
1747 ms
optout_check
1428 ms
get
1379 ms
ca-pub-2051007210431666.js
1524 ms
ads
1244 ms
osd.js
767 ms
p.media
688 ms
p.media
1201 ms
p.media
1300 ms
p.media
1075 ms
p.media
1158 ms
p.media
1072 ms
p.media
1223 ms
p.media
1159 ms
p.media
1252 ms
rrum
1568 ms
ad
2872 ms
m_qs_click_protection.js
1119 ms
Pug
3503 ms
i.match
1238 ms
hmac-sha1.js
1343 ms
i.match
4599 ms
transparent.png
1636 ms
usermatch
2069 ms
tap.php
1039 ms
activeview
1035 ms
cookie_push.html
1354 ms
ba1453ba-93b2-476c-8e2d-4d7b2691ae61.jpg
5226 ms
everquote.png
3242 ms
pixel
752 ms
casale
752 ms
i.match
3390 ms
crum
2649 ms
crum
2566 ms
crum
2651 ms
i.match
3008 ms
utsync.ashx
6918 ms
crum
1821 ms
ext.js
1654 ms
runtime.js
3170 ms
sd
1051 ms
i.match
2103 ms
crum
2084 ms
crum
5089 ms
crum
4445 ms
activeview
4039 ms
rum
4039 ms
activeview
3413 ms
activeview
3395 ms
pixel
140 ms
sync
444 ms
sync
398 ms
saskobits.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
saskobits.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
saskobits.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Saskobits.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 Saskobits.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.
saskobits.com
Open Graph data is detected on the main page of Saskobits. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: