3.3 sec in total
318 ms
2.1 sec
844 ms
Welcome to rootsy.com homepage info - get ready to check Rootsy best content right away, or after learning these important things about rootsy.com
Discover the latest breaking news in the U.S. and around the world — politics, weather, entertainment, lifestyle, finance, sports and much more.
Visit rootsy.comWe analyzed Rootsy.com page load time and found that the first response time was 318 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
rootsy.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value8.4 s
2/100
25%
Value11.6 s
4/100
10%
Value5,210 ms
0/100
30%
Value0.022
100/100
15%
Value20.8 s
2/100
10%
318 ms
18 ms
32 ms
88 ms
33 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Rootsy.com, 17% (15 requests) were made to Xyz.aolcdn.com and 14% (13 requests) were made to Blogsmithmedia.com. The less responsive or slowest element that took the longest time to load (563 ms) relates to the external source Cdn.taboola.com.
Page size can be reduced by 1.1 MB (55%)
2.0 MB
891.2 kB
In fact, the total size of Rootsy.com main page is 2.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. 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 646.0 kB which makes up the majority of the site volume.
Potential reduce by 437.9 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 437.9 kB or 87% of the original size.
Potential reduce by 24.8 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. Rootsy images are well optimized though.
Potential reduce by 425.6 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 425.6 kB or 66% of the original size.
Potential reduce by 214.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. Rootsy.com needs all CSS files to be minified and compressed as it can save up to 214.1 kB or 85% of the original size.
Number of requests can be reduced by 36 (43%)
83
47
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rootsy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
www.aol.com
318 ms
application.css
18 ms
legacy_ads.css
32 ms
homepage-grid.css
88 ms
adsWrapper.js
33 ms
omniture.min.js
37 ms
jquery-1.12.0.min.js
39 ms
jquery.jcarousel.min.js
32 ms
shared.js
18 ms
aol-feedback-loader-latest.min.js
299 ms
grid.min.js
301 ms
hub-controller.js
17 ms
moatuac.js
560 ms
loader.js
563 ms
aol-logo-black.png
209 ms
blank.gif
432 ms
aol-logo-white.svg
428 ms
blank.gif
435 ms
inside.png
435 ms
1AC2.jpg
513 ms
loading-1.svg
424 ms
adpage.html
424 ms
2DE4E0_4_0.woff
430 ms
2DE4E0_2_0.woff
430 ms
icons.woff
431 ms
2DE4E0_1_0.woff
427 ms
bon-grid-icons.woff
432 ms
gdk-0.2.5-bare.min.js
339 ms
132 ms
th
115 ms
5.jpg
106 ms
80C1.jpg
127 ms
2D2F.jpg
126 ms
9406.jpg
125 ms
81CA.jpg
129 ms
6D87.jpg
132 ms
4890.jpg
132 ms
C9D5.jpg
131 ms
A762.jpg
127 ms
835E.jpg
132 ms
116 ms
120 ms
119 ms
_12164800.jpg
119 ms
iphor3009616750_q2_1-0._QL90_UX336_.jpg
124 ms
_11494032.jpg
119 ms
rmink4454211873_q1_1-0._QL90_UX336_.jpg
119 ms
th
101 ms
th
115 ms
th
112 ms
th
114 ms
rd
103 ms
26.svg
82 ms
14.svg
83 ms
34.svg
80 ms
allowedSizes=728x90,948x250,950x252,940x230,101x1,970x66,970x90,970x250;cfp=1;rndc=1458477878;noperf=1;alias=93320497;noaddonpl=y;artexc=art_flash,art_rrflash;kvblogname=news;kvcategory=mainpage;kvpg=aol;kvugc=0;kvh5lsid=0;kvmn=93320497;kvgrp=477878216;kvismob=2;extmirroring=0;kvtile=1;target=_blank;aduho=180;grp=477878216
79 ms
noperf=1;cfp=1;rndc=1458477878;alias=93315260;noaddonpl=y;artexc=art_flash,art_rrflash;kvblogname=news;kvcategory=mainpage;kvpg=aol;kvugc=0;kvh5lsid=0;kvmn=93315260;kvgrp=477878216;kvismob=2;extmirroring=0;kvtile=3;target=_blank;aduho=180;grp=477878216
72 ms
70 ms
beacon.min.js
71 ms
id
55 ms
pixel.gif
35 ms
impl.201-1-RELEASE.js
43 ms
beacon.js
41 ms
recommendations
166 ms
adServer.bs
91 ms
AdId=7968082;BnId=2;ct=1474464526;st=2786;adcid=1;itime=477878591;reqtype=5;;impref=1458477878235838232;imprefseq=155095031651251134;imprefts=1458477878;kp=256527;
29 ms
2DDBD6_4_0.woff
25 ms
75 ms
s45934037435799
65 ms
pixel.gif
4 ms
B9478575.128839107;dc_trk_aid=301774437;dc_trk_cid=69033151;ord=436712392;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=
90 ms
backup.jpg
89 ms
json
40 ms
ive
78 ms
adchoices.png
11 ms
439b05c810c582a6090665fa59eb97ca.png
17 ms
f3bb7e481660086afe7b748d4c6abb8a.jpg
13 ms
2-pool.jpg
12 ms
guid.html
31 ms
tcode3.html
37 ms
sn_sync.html
30 ms
slf.js
16 ms
916f392e-1af6-43dd-bc12-239421d8b718.js
28 ms
tcodeqt.html
14 ms
slf.js
6 ms
r.js
25 ms
sn_sync-built.js
13 ms
916f392e-1af6-43dd-bc12-239421d8b718
17 ms
9e865b16-bf55-4ffb-9f2a-70dadfc986c7.js
22 ms
edfa959e-e215-4912-a503-4f286422a835.js
23 ms
rootsy.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
rootsy.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
rootsy.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Rootsy.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 Rootsy.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.
rootsy.com
Open Graph description is not detected on the main page of Rootsy. 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: