2.6 sec in total
508 ms
1.9 sec
224 ms
Click here to check amazing Datingme content. Otherwise, check out these important facts you probably never knew about datingme.org
Visit datingme.orgWe analyzed Datingme.org page load time and found that the first response time was 508 ms and then it took 2.1 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.
datingme.org performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value5.4 s
20/100
25%
Value6.5 s
39/100
10%
Value30 ms
100/100
30%
Value0.017
100/100
15%
Value5.9 s
65/100
10%
508 ms
64 ms
80 ms
159 ms
158 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 45% of them (24 requests) were addressed to the original Datingme.org, 28% (15 requests) were made to Galcdn.datingfactory.net and 9% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (508 ms) belongs to the original domain Datingme.org.
Page size can be reduced by 298.0 kB (24%)
1.2 MB
935.5 kB
In fact, the total size of Datingme.org main page is 1.2 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. 50% of websites need less resources to load. Images take 802.2 kB which makes up the majority of the site volume.
Potential reduce by 27.0 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 4.0 kB, which is 11% 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 27.0 kB or 78% of the original size.
Potential reduce by 3.4 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. Datingme images are well optimized though.
Potential reduce by 252.9 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 252.9 kB or 67% of the original size.
Potential reduce by 14.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. Datingme.org needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 81% of the original size.
Number of requests can be reduced by 23 (49%)
47
24
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Datingme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.datingme.org
508 ms
css
64 ms
normalize.min.css
80 ms
foundation.min.css
159 ms
owl.carousel.css
158 ms
index.common.css
164 ms
index.css
162 ms
df.js
362 ms
theme.js
187 ms
Index.js
231 ms
modernizr.min.js
232 ms
fastclick.min.js
238 ms
owl.carousel.min.js
240 ms
b4a0494899b9a9a5505830274d13e27e.png
128 ms
visual.jpg
339 ms
logo.png
87 ms
story1.jpg
89 ms
story2.jpg
106 ms
story3.jpg
105 ms
9d2f04fc1e9ddabc3c895938a20eca79.png
127 ms
69637848db2a2822c24fb8db93e45d29.png
158 ms
ba4615a79354a90e5e7bb3ebb9db1a70.png
164 ms
1627981305bc5cf57d5f75141229d879.png
130 ms
46857c5c5b14dc7cde9c6922ca7ae552.png
166 ms
7269cd1a0f0efae8273a4e668b2bcffa.png
222 ms
bfe18b2ecee94d213ba30c40c30b0153.png
222 ms
0a15943f50ab01a5e2bdd5071f03eead.png
223 ms
302ec4a4e6ae4b6ccfac419e7a3391ca.png
222 ms
5b418ac7dea0cc877ced128c9c378740.png
241 ms
bb94553fe09432730ae92bf8c35da347.png
301 ms
49810c4db005728cc6dc3f6ff2439b39.png
235 ms
33264876ba1943f3c8d16509f42c18dc.png
236 ms
93d214667143082a37720300fe5046e0.png
236 ms
SwitchLocale.js
90 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
28 ms
Uxzkqj-MIMWle-XP2pDNAA.ttf
36 ms
7MygqTe2zs9YkP0adA9QQQ.ttf
47 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
48 ms
selector_arrow_bottom.gif
122 ms
RegistrationShort.js
84 ms
select-arrow.png
107 ms
ico_warning.gif
104 ms
members-h2-bkg.png
105 ms
analytics.js
6 ms
visitx-link-bk-010.php
480 ms
ga.js
13 ms
collect
69 ms
__utm.gif
9 ms
__utm.gif
14 ms
regform-dl-bkg.png
83 ms
ajs.php
249 ms
collect
51 ms
lg.php
92 ms
datingme.org 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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
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.
datingme.org 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
Issues were logged in the Issues panel in Chrome Devtools
datingme.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
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 Datingme.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 Datingme.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.
datingme.org
Open Graph description is not detected on the main page of Datingme. 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: