2.3 sec in total
36 ms
1.4 sec
841 ms
Click here to check amazing Obits Roanoke content for United States. Otherwise, check out these important facts you probably never knew about obits.roanoke.com
Find Roanoke Times Obituaries and death notices from Roanoke, VA funeral homes and newspapers. Discover the latest obits this week, including today's.
Visit obits.roanoke.comWe analyzed Obits.roanoke.com page load time and found that the first response time was 36 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
obits.roanoke.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value33.4 s
0/100
25%
Value26.7 s
0/100
10%
Value11,710 ms
0/100
30%
Value0.176
68/100
15%
Value53.0 s
0/100
10%
36 ms
131 ms
33 ms
28 ms
45 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Obits.roanoke.com, 6% (7 requests) were made to Roanoke.com and 6% (7 requests) were made to Cdn.oas-c18.adnxs.com. The less responsive or slowest element that took the longest time to load (314 ms) relates to the external source Connect.facebook.net.
Page size can be reduced by 1.7 MB (65%)
2.6 MB
902.0 kB
In fact, the total size of Obits.roanoke.com main page is 2.6 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 275.7 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. This page needs HTML code to be minified as it can gain 97.9 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 275.7 kB or 85% of the original size.
Potential reduce by 46.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. Obviously, Obits Roanoke needs image optimization as it can save up to 46.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 839.7 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 839.7 kB or 67% of the original size.
Potential reduce by 488.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. Obits.roanoke.com needs all CSS files to be minified and compressed as it can save up to 488.7 kB or 86% of the original size.
Number of requests can be reduced by 69 (59%)
116
47
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Obits Roanoke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
obituaries
36 ms
131 ms
jquery-ui-default.min.css
33 ms
ads.min.css
28 ms
ads_demo.min.css
45 ms
navigation.core.css
43 ms
navigation.mega.css
45 ms
navigation.header-top.css
46 ms
styles.min.css
53 ms
_switcher.css
46 ms
navigation.accordion.css
81 ms
site.css
44 ms
yepnope.min.js
84 ms
jquery.min.js
99 ms
jquery-ui.min.js
99 ms
user.js
145 ms
ads_expandable.js
146 ms
ads_page_curl.js
144 ms
ads_text.js
143 ms
jquery.cookie.js
147 ms
jquery.hoverintent.min.js
145 ms
navigation.mega.js
147 ms
tracking.js
149 ms
tncms-ad-limits.js
148 ms
ads.js
150 ms
jquery.lazyload.js
149 ms
navigation.accordion.js
146 ms
jquery.frame.js
148 ms
cc.js
174 ms
var=ccauds
167 ms
css
170 ms
tracker.js
185 ms
section-sponsor1.js
108 ms
Widgets.js
112 ms
external.common.min.js
106 ms
global.extensions.js
105 ms
global.extensions.jquery.js
105 ms
blox.scripts.js
105 ms
yepnope.scripts.js
107 ms
flowplayer-3.2.13.min.js
107 ms
embed.js
100 ms
beacon.js
28 ms
prum.min.js
31 ms
2.png
23 ms
rss-icon.gif
35 ms
56ee12451efd9.image.jpg
23 ms
56ee1244c1aec.image.jpg
24 ms
56ee1244efcca.image.jpg
25 ms
56ecc208be226.image.jpg
25 ms
56eb6f8f07c40.image.jpg
26 ms
56eb6f8e52be3.image.jpg
26 ms
56eb6f8e67dc0.image.jpg
26 ms
56eb6f8e05526.image.jpg
27 ms
56ea1eb8392bd.image.jpg
29 ms
56ea1eb7abedc.image.jpg
28 ms
56ea1ebabcd8e.image.jpg
29 ms
56ea1eb9b8356.image.jpg
29 ms
56ea1eb756ec7.image.jpg
30 ms
56ea1eb971081.image.jpg
29 ms
56ea1eba3d739.image.jpg
30 ms
56e8cd6eddaa6.image.jpg
30 ms
56e8cd6e7ca6f.image.jpg
32 ms
56e8cd6e3c0bf.image.jpg
31 ms
56e77b67299cf.image.jpg
32 ms
56c39644775f1.image.jpg
30 ms
5651270b8f08b.image.jpg
33 ms
5643fe5c44b0a.image.jpg
33 ms
561be539f1ec2.image.jpg
32 ms
52f2825960783.preview-200.jpg
34 ms
52d5b3812690a.preview-200.jpg
34 ms
542af176bfeb9.preview-200.jpg
34 ms
32 ms
callback=_nw2e.closures.c0
28 ms
ajax-loader.gif
4 ms
roanoke-times-logo-2015.png
13 ms
subNEW.png
20 ms
rxxXUYj4oZ6Q5oDJFtEd6i3USBnSvpkopQaUR-2r7iU.ttf
5 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
8 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
15 ms
1958322802@Top,Right,Right1,Right2,Bottom,BottomLeft,Top1,Right3!Top
49 ms
1455566458
114 ms
1455566458
137 ms
1958322802@Top,Right,Right1,Right2,Bottom,BottomLeft,Top1,Right3!Top1
10 ms
empty.gif
71 ms
1958322802@Top,Right,Right1,Right2,Bottom,BottomLeft,Top1,Right3!Middle
10 ms
ui-bg_flat_75_ffffff_40x100.png
52 ms
related-sprite.png
30 ms
1958322802@Top,Right,Right1,Right2,Bottom,BottomLeft,Top1,Right3!Right
21 ms
bbqcard_300x250.jpg
50 ms
bg-heading.gif
7 ms
tn-common-icons.png
266 ms
1958322802@Top,Right,Right1,Right2,Bottom,BottomLeft,Top1,Right3!Right1
10 ms
ROA_NationalOptical_300x250_262525-02.jpg
27 ms
1958322802@Top,Right,Right1,Right2,Bottom,BottomLeft,Top1,Right3!Right2
10 ms
300x250.jpg
65 ms
EmailSignup.aspx
239 ms
1958322802@Top,Right,Right1,Right2,Bottom,BottomLeft,Top1,Right3!Bottom
12 ms
trt_fb.png
39 ms
trt_tw.png
34 ms
trt_in.png
34 ms
ROA_EVERGREEN_728X90.jpg
51 ms
quant.js
118 ms
jquery.floatingfixed.js
112 ms
analytics.js
109 ms
dc.js
128 ms
ui-bg_glass_75_e6e6e6_1x400.png
76 ms
addthis_widget.js
70 ms
all.js
314 ms
getids
32 ms
ui-icons_888888_256x240.png
9 ms
pixel;r=1086016110;a=p-f5LbblMdUG-tM;fpan=1;fpa=P0-659009212-1458489732734;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458489732734;tzo=-180;ref=;url=http%3A%2F%2Fwww.roanoke.com%2Fobituaries%2F;ogl=title.Roanoke%20Times%2Csite_name.www%252Eroanoke%252Ecom%2Cimage.http%3A%2F%2Fwww%252Eroanoke%252Ecom%2Fapp%2Fassets%2Fimages%2Fgeneral%2FTRTFBog%252Epng%2Curl.http%3A%2F%2Fwww%252Eroanoke%252Ecom%2Fobituaries%2F%2Cdescription.News%252C%20weather%252C%20and%20sports%20in%20Roanoke%20and%20Blacksburg%252C%20VA%2Ctype.website
24 ms
collect
12 ms
jquery.floatingfixed.js
9 ms
SkinBase.css
47 ms
SkinLight.css
57 ms
SiteJS.js
160 ms
dc.js
10 ms
__utm.gif
16 ms
inpage_linkid.js
7 ms
addthis_widget.js
10 ms
all.js
166 ms
obits.roanoke.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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.
obits.roanoke.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Missing source maps for large first-party JavaScript
obits.roanoke.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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Obits.roanoke.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 Obits.roanoke.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
obits.roanoke.com
Open Graph data is detected on the main page of Obits Roanoke. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: