1.6 sec in total
82 ms
1.4 sec
115 ms
Click here to check amazing Dating Aarp content for United States. Otherwise, check out these important facts you probably never knew about dating.aarp.org
Visit dating.aarp.orgWe analyzed Dating.aarp.org page load time and found that the first response time was 82 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
dating.aarp.org performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value15.6 s
0/100
25%
Value11.0 s
6/100
10%
Value5,420 ms
0/100
30%
Value0.074
95/100
15%
Value37.7 s
0/100
10%
82 ms
41 ms
7 ms
5 ms
5 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 11% of them (14 requests) were addressed to the original Dating.aarp.org, 15% (19 requests) were made to Assets.adobedtm.com and 12% (16 requests) were made to Cdn.aarp.net. The less responsive or slowest element that took the longest time to load (425 ms) relates to the external source Analytics.twitter.com.
Page size can be reduced by 3.4 MB (72%)
4.7 MB
1.3 MB
In fact, the total size of Dating.aarp.org main page is 4.7 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. 80% 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 3.5 MB which makes up the majority of the site volume.
Potential reduce by 23.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 23.5 kB or 67% of the original size.
Potential reduce by 2.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. Obviously, Dating Aarp needs image optimization as it can save up to 2.3 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.5 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 2.5 MB or 73% of the original size.
Potential reduce by 814.8 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. Dating.aarp.org needs all CSS files to be minified and compressed as it can save up to 814.8 kB or 71% of the original size.
Number of requests can be reduced by 82 (72%)
114
32
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dating Aarp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
dating.aarp.org
82 ms
middle_screen-fc047c740c8bcf9be46c0814906b2d41.css
41 ms
aarp.css
7 ms
modernizr-3c65a72a9ac2211ebe36865acef8be23.js
5 ms
bridge.js
5 ms
jquery.min.js
40 ms
landing-8b19dcbd7858fc47c0778ecd3fae4686.js
40 ms
aarp-49fcd3dcb0d59cfc6480d2bb637f476e.js
7 ms
elvis.js
18 ms
21180258.js
319 ms
elvis.js
124 ms
gtm.js
72 ms
aarp
119 ms
aarp-site-header.png
13 ms
CharisSILR-webfont.woff
10 ms
fetteengd-webfont-25ca14be0c33db99c020c0cf26a40991.woff
11 ms
hawdating-webfont-250865c5d5c01aff7e9442271aaa3d84.woff
11 ms
easyXDM.min.js
11 ms
elvis_core.js
11 ms
icon1.png
8 ms
easyXDM.min.js
2 ms
elvis_core.js
5 ms
18 ms
event.php
199 ms
analytics.js
28 ms
conversion_async.js
29 ms
sp.js
25 ms
activityi;src=3224370;type=landi336;cat=homep036;ord=6965388792963;~oref=http%3A%2F%2Fdating.aarp.org%2F
30 ms
147 ms
gigya.js
52 ms
global.rev20160218135448.css
76 ms
components.rev20160218135448.css
82 ms
registration.rev20160218135448.css
75 ms
satelliteLib-42020ba8ae7a978d8dc6847e6390647fd55e69a2.js
137 ms
global.rev20160218135448.js
75 ms
foresee-alive.imgcache.rev20160218135448.js
136 ms
addthis_widget.js
159 ms
drewards.rev20160218135448.js
158 ms
px
153 ms
display.js
163 ms
i
126 ms
collect
125 ms
collect
313 ms
156 ms
controltag
369 ms
global.rev10676.js
80 ms
1.0.js
336 ms
ajax-loader-dark.gif
51 ms
adsct
425 ms
id
40 ms
mbox-contents-9d387c91fef6bae38e0346c1d25e686ea158b5ab.js
24 ms
freigtexpromed-webfont-a816b687c47213982943db04fb7d331f.woff
19 ms
null.gif
187 ms
dis.aspx
185 ms
target.js
57 ms
id
161 ms
317 ms
gpt.js
274 ms
omniture.js
221 ms
sprite-icon_social.imgcache.rev20160218135448.png
112 ms
separator_subhat-dotted.imgcache.rev20160218135448.png
113 ms
arrow_subhat-sprite.imgcache.rev20160218135448.png
113 ms
sprite-bg_header.imgcache.rev20160218135448.png
111 ms
bg_standoutCorner.imgcache.rev20160218135448.png
112 ms
logo_aarp.imgcache.rev20160218135448.png
162 ms
aarp_dating_no_disclaimer.imgcache.rev1348169972355.web.png
162 ms
satellite-54d5496930616600190e0000.js
133 ms
satellite-54249166fcc89a9f3e000160.js
132 ms
satellite-54daa4ad3034620019ac0800.html
128 ms
satellite-530673b5e570c3cec6000116.js
140 ms
satellite-564f359564746d2b720001a7.html
137 ms
satellite-564f3d8264746d35ef000219.html
136 ms
satellite-55b6387b30626100170005b2.html
133 ms
satellite-55b169683739320014000c85.html
134 ms
satellite-55b16906306338001700007c.html
133 ms
satellite-5564a0993064310014710500.html
134 ms
satellite-5564a4443064311a484a0200.html
133 ms
satellite-556735573138360017140500.html
132 ms
satellite-56688dcb64746d342d005ac9.js
130 ms
satellite-564ea36564746d727e000c03.html
133 ms
satellite-569f6aa664746d5f2f000372.html
130 ms
satellite-569f40c464746d2db2000205.html
131 ms
gtm.js
67 ms
bg_channel-active.imgcache.rev20160218135448.png
58 ms
pixel
159 ms
controltag.js.3269b976cac0388f80dbfdb09d96a4e7
92 ms
aTZQR2JCbTJsNkE9
172 ms
fbds.js
105 ms
pubads_impl_81.js
42 ms
aarp
183 ms
32 ms
oct.js
83 ms
B8608412.116253227;dcadv=4757604;sz=1x2;ord=741261028451.8451
164 ms
bat.js
102 ms
ytc.js
137 ms
spp.pl
208 ms
conversion.js
81 ms
IOD67BELXBAVZJIVG4WA6S
111 ms
ajax
66 ms
fbevents.js
88 ms
r
10 ms
container.html
104 ms
container.html
113 ms
adsct
71 ms
adsct
85 ms
adsct
83 ms
adsct
88 ms
adsct
87 ms
adsct
109 ms
pxgcm
84 ms
124 ms
149 ms
28 ms
157 ms
json
56 ms
out
31 ms
46 ms
u.php
58 ms
conversion.js
49 ms
bat.js
57 ms
51 ms
19 ms
25 ms
pxfbcm
10 ms
pxfbcm
4 ms
pixel
22 ms
nr-885.min.js
58 ms
satellite-56b8911c64746d730700001c.js
43 ms
optout_check
39 ms
299cfae0b7
58 ms
299cfae0b7
56 ms
dating.aarp.org 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
[aria-hidden="true"] elements contain focusable descendents
dating.aarp.org 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
dating.aarp.org 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dating.aarp.org 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 Dating.aarp.org 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.
dating.aarp.org
Open Graph description is not detected on the main page of Dating Aarp. 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: