37.3 sec in total
545 ms
25.5 sec
11.2 sec
Click here to check amazing Who S Dated content for United States. Otherwise, check out these important facts you probably never knew about whosdatedwho.com
Visit whosdatedwho.comWe analyzed Whosdatedwho.com page load time and found that the first response time was 545 ms and then it took 36.7 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.
whosdatedwho.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value8.1 s
2/100
25%
Value7.2 s
30/100
10%
Value12,980 ms
0/100
30%
Value0
100/100
15%
Value25.3 s
0/100
10%
545 ms
1020 ms
1562 ms
2013 ms
2012 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Whosdatedwho.com, 21% (11 requests) were made to Cdnjs.cloudflare.com and 13% (7 requests) were made to Img3.bdbphotos.com. The less responsive or slowest element that took the longest time to load (7.5 sec) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 2.5 MB (61%)
4.0 MB
1.6 MB
In fact, the total size of Whosdatedwho.com main page is 4.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. 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. CSS take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 51.3 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 12.1 kB, which is 21% 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 51.3 kB or 89% of the original size.
Potential reduce by 60.2 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. Who S Dated images are well optimized though.
Potential reduce by 696.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 696.5 kB or 66% of the original size.
Potential reduce by 1.6 MB
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. Whosdatedwho.com needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 80% of the original size.
Number of requests can be reduced by 21 (42%)
50
29
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Who S Dated. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
whosdatedwho.com
545 ms
www.whosdatedwho.com
1020 ms
foundation.min.css
1562 ms
normalize.min.css
2013 ms
jquery-ui.min.css
2012 ms
swiper.min.css
1980 ms
1172 ms
jquery-2.1.4.min.js
3170 ms
adsbygoogle.js
686 ms
foundation.min.js
2857 ms
modernizr.min.js
2857 ms
js
1124 ms
firebase.js
3815 ms
swiper.min.js
2856 ms
jquery-ui.min.js
2857 ms
hammer.min.js
2856 ms
jquery.cookie.min.js
2855 ms
jquery.infinitescroll.min.js
3804 ms
js
1122 ms
quant.js
1667 ms
wdw.png
691 ms
1nkv8trg975658t.jpg
990 ms
8ydkvwz8p3lgvl8.jpg
740 ms
xmwd86432230386.jpg
990 ms
82al7st8zimtszat.jpg
739 ms
j7gvozpqz7ivzvzg.jpg
703 ms
7stq9emnkmfwektw.jpg
952 ms
9m71iuku2kg6u62.jpg
719 ms
f5g303adyq87aq3f.jpg
952 ms
9j36i2joti8o6ij.jpg
953 ms
axaqjksgd4fm4dmk.jpg
888 ms
24gfs4aseayo2oge.jpg
690 ms
47a0fy9xinev9yia.jpg
690 ms
xxeokwgp1exrwkpx.jpg
833 ms
0m4ev8ldt2jt0t4t.jpg
3783 ms
rjotynogvtepgott.jpg
3765 ms
hvaaw2a19o6hvhao.jpg
3801 ms
4zxj4w0yrscojxwo.jpg
3763 ms
kaoacvng6tcekeo6.jpg
3800 ms
75l2pp39ik5jkijp.jpg
3701 ms
jpuh4tg95v5vt49p.jpg
3801 ms
7h2224ylh6gv6hv4.jpg
3800 ms
e4d2qa8p36ft3pfq.jpg
3701 ms
5tf13rg81u8f1883.jpg
3788 ms
ca-pub-4356445222935173.js
4254 ms
zrt_lookup.html
7499 ms
show_ads_impl.js
5135 ms
ff-icon-set.woff
3455 ms
pla
1181 ms
ajax-loader-fff.gif
433 ms
analytics.js
380 ms
rules-p-903bQOpJXvFzg.js
244 ms
sdk.js
2804 ms
whosdatedwho.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.
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
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
whosdatedwho.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
whosdatedwho.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whosdatedwho.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 Whosdatedwho.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.
whosdatedwho.com
Open Graph description is not detected on the main page of Who S Dated. 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: