2.8 sec in total
348 ms
1.5 sec
1 sec
Click here to check amazing When Dating content for United States. Otherwise, check out these important facts you probably never knew about whendating.com
Visit whendating.comWe analyzed Whendating.com page load time and found that the first response time was 348 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
whendating.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value9.0 s
1/100
25%
Value6.8 s
35/100
10%
Value490 ms
59/100
30%
Value0
100/100
15%
Value8.7 s
36/100
10%
348 ms
12 ms
20 ms
10 ms
35 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Whendating.com, 19% (11 requests) were made to 38.media.tumblr.com and 16% (9 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (766 ms) relates to the external source Px.srvcs.tumblr.com.
Page size can be reduced by 696.0 kB (33%)
2.1 MB
1.4 MB
In fact, the total size of Whendating.com main page is 2.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. 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. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 84.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. This page needs HTML code to be minified as it can gain 17.0 kB, which is 17% 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 84.8 kB or 86% of the original size.
Potential reduce by 621 B
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. When Dating images are well optimized though.
Potential reduce by 585.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 585.5 kB or 64% of the original size.
Potential reduce by 25.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. Whendating.com needs all CSS files to be minified and compressed as it can save up to 25.1 kB or 81% of the original size.
Number of requests can be reduced by 20 (36%)
56
36
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of When Dating. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
whendating.com
348 ms
pre_tumblelog.js
12 ms
reset.css
20 ms
font-awesome.css
10 ms
jquery.min.js
35 ms
jquery.timeago.js
90 ms
css
27 ms
jquery.infinitescroll.min.js
21 ms
run_prettify.js
84 ms
pretty-theme.css
18 ms
tumblelog_post_message_queue.js
16 ms
stylesheet.css
16 ms
tweets.js
311 ms
pxuphotoset.min.js
20 ms
index.js
21 ms
prettify.css
12 ms
tumblr_static_jpeg.png
71 ms
tumblr_inline_o1ogdkhelr1snq3fu_500.gif
69 ms
like_iframe.html
60 ms
tumblr_inline_o3s0tzcrWo1snq3fu_500.gif
342 ms
tumblr_o1l4emGDco1tn3skko1_250.gif
75 ms
tumblr_o1l4emGDco1tn3skko2_250.gif
440 ms
tumblr_inline_o47c8nVF3x1r79k32_500.gif
311 ms
tumblr_o472h54NNn1ql5yr7o3_500.gif
608 ms
tumblr_o472h54NNn1ql5yr7o1_500.gif
607 ms
tumblr_inline_o3scdpOUNY1ro2d43_500.gif
439 ms
tumblr_inline_o3scdvhyUR1ro2d43_500.gif
476 ms
tumblr_m26ytk2z4e1qih5mn.gif
515 ms
tumblr_inline_o47h5l6eeZ1rrdow9_500.gif
517 ms
tumblr_nnlnhvqM4Y1qk08n1o1_500.gif
701 ms
tumblr_nnyl7leSlP1qk08n1o1_400.gif
605 ms
tumblr_inline_o3scdkBRr61ro2d43_500.gif
48 ms
tumblr_inline_o421bwzAOk1ro2d43_500.gif
52 ms
tumblr_inline_mv3ls8tIDJ1rkz2gy.gif
39 ms
tumblr_inline_o47gpvyyVk1rrdow9_500.gif
58 ms
tumblr_inline_o47fzsRvvy1rrdow9_500.gif
45 ms
tumblr_mimtanqgKQ1ql5yr7o1_400.gif
54 ms
tumblr_static_jpeg-1.png
52 ms
avatar.png
34 ms
fontawesome-webfont.woff
3 ms
BkSPb85m_normal.jpeg
109 ms
analytics.js
104 ms
impixu
766 ms
impixu
537 ms
analytics.html
48 ms
login_check.html
16 ms
collect
17 ms
rapid-3.36.js
39 ms
rapidworker-1.2.js
46 ms
ga.js
62 ms
analytics.js
87 ms
cs.js
56 ms
addthis.html
93 ms
__utm.gif
20 ms
addthis_widget.js
41 ms
api.html
54 ms
load.gif
4 ms
cedexis.radar.js
4 ms
whendating.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
whendating.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
whendating.com SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whendating.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 Whendating.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.
whendating.com
Open Graph description is not detected on the main page of When Dating. 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: