2.8 sec in total
688 ms
2 sec
168 ms
Click here to check amazing Xp Dating content. Otherwise, check out these important facts you probably never knew about xpdating.com
Want to know the key to online dating success? Read our guide to increase your chances!
Visit xpdating.comWe analyzed Xpdating.com page load time and found that the first response time was 688 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.
xpdating.com performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value3.8 s
54/100
25%
Value2.7 s
97/100
10%
Value110 ms
98/100
30%
Value0.002
100/100
15%
Value3.5 s
92/100
10%
688 ms
181 ms
164 ms
381 ms
199 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 35% of them (16 requests) were addressed to the original Xpdating.com, 22% (10 requests) were made to Galcdn.datingfactory.net and 17% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (688 ms) belongs to the original domain Xpdating.com.
Page size can be reduced by 89.9 kB (18%)
501.0 kB
411.1 kB
In fact, the total size of Xpdating.com main page is 501.0 kB. 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 352.5 kB which makes up the majority of the site volume.
Potential reduce by 47.4 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 47.4 kB or 75% of the original size.
Potential reduce by 1.9 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. Xp Dating images are well optimized though.
Potential reduce by 40.7 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 40.7 kB or 48% of the original size.
Number of requests can be reduced by 23 (53%)
43
20
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xp 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 19 to 1 for JavaScripts and as a result speed up the page load time.
www.xpdating.com
688 ms
index.common.css
181 ms
index.css
164 ms
df.js
381 ms
theme.js
199 ms
Index.js
157 ms
cookieconsent.min.js
41 ms
platform.js
80 ms
analytics.js
15 ms
87fba265dfd51d78ca404a80aa201f22.png
65 ms
efa673ada130bbf58df732b50887d3eb.png
64 ms
7664c1a898916b4b58a97d961e1f776e.png
54 ms
afdf094f8c42cbbc66315365072b001d.png
68 ms
cb112604ec52d7e92ecfa55b9b0842c7.png
67 ms
9bb31b89883dbdf7811c3f2a0dd0961c.png
68 ms
68cdf0d57c33194c15fc785c7ead978a.png
79 ms
9af21760b64fd502f93afe6e50c35ee6.png
90 ms
71b7d6097dd5b391b893d0210b1f99f4.png
91 ms
8eb89cf2dd2485477182fd427f6106ef.png
504 ms
logo.png
90 ms
hollow.gif
89 ms
SwitchLocale.js
79 ms
collect
10 ms
selector_arrow_bottom.gif
83 ms
ID-10085918.jpg
418 ms
RegistrationSimple.js
80 ms
jquery.select.behavior.js
96 ms
ico_warning.gif
169 ms
widgets.js
176 ms
cb=gapi.loaded_0
17 ms
cb=gapi.loaded_1
15 ms
fastbutton
144 ms
collect
54 ms
ga.js
54 ms
postmessageRelay
152 ms
__utm.gif
59 ms
icon_auth.png
116 ms
providers.gif
116 ms
cb=gapi.loaded_0
61 ms
cb=gapi.loaded_1
63 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
92 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
143 ms
collect
90 ms
3193398744-postmessagerelay.js
46 ms
rpc:shindig_random.js
41 ms
cb=gapi.loaded_0
3 ms
xpdating.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Buttons do not have an accessible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
xpdating.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
xpdating.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xpdating.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 Xpdating.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.
xpdating.com
Open Graph description is not detected on the main page of Xp 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: