xdate.ch

xdate.ch is SSL secured

Free website and domain report on xdate.ch

Last Updated: 30th September, 2022 Update Now
Overview

Snoop Summary for xdate.ch

This is a free and comprehensive report about xdate.ch. Xdate.ch is hosted in United States on a server with an IP address of 104.18.168.23, where USD is the local currency and the local language is English. Our records indicate that xdate.ch is owned/operated by Cloudflare, Inc.. Xdate.ch is expected to earn an estimated $64 USD per day from advertising revenue. The sale of xdate.ch would possibly be worth $46,629 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Xdate.ch receives an estimated 15,101 unique visitors every day - a huge amount of traffic! This report was last updated 30th September, 2022.

About xdate.ch

Site Preview:
Title: xdate.ch ▷ Das schweizer Sex und Erotik Inserate Portal.
Description: ★★★ Die besten Sex & Erotik Anzeigen der Schweiz: Für jeden Geschmack! ♥ Anrufen & vorbeikommen! xdate.ch ▷ Das Schweizer Sex & Erotik Inserate Portal.
Keywords and Tags: adult content, popular, pornography
Related Terms: anzeigen, erotik, erotik beratung, erotik finden, erotik kleinanzeigenmarkt, erotik sayt, erotik webdesign, schweizer, schweizer berge, schweizer fernsehen
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

3/5 (Great!)

Valuation

$46,629 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 41,153
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 15,101
Monthly Visitors: 459,631
Yearly Visitors: 5,511,917
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $64 USD
Monthly Revenue: $1,944 USD
Yearly Revenue: $23,309 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: xdate.ch 8
Domain Name: xdate 5
Extension (TLD): ch 2

Page Speed Analysis

Average Load Time: 0.61 seconds
Load Time Comparison: Faster than 93% of sites

PageSpeed Insights

Avg. (All Categories) 85
Performance 97
Accessibility 68
Best Practices 92
SEO 100
PWA 67
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.xdate.ch/
Updated: 30th September, 2022

0.74 seconds
First Contentful Paint (FCP)
96%
3%
1%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

97

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for xdate.ch. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 1.5 s
The time taken for the page to become fully interactive.
Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 10 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 1.0 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 70 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://xdate.ch/
http/1.1
0
58.945000171661
384
0
301
text/plain
https://www.xdate.ch/
h2
59.241000097245
412.54599997774
34756
232066
200
text/html
Document
https://fonts.googleapis.com/css2?family=Inter:wght@400;600;700&display=swap
h2
423.65199979395
434.5920002088
1436
6846
200
text/css
Stylesheet
https://www.xdate.ch/build/app.css?v112
h2
423.78199985251
537.40999987349
63627
330163
200
text/css
Stylesheet
https://www.xdate.ch/build/app-sm-up.css?v112
h2
424.91400009021
514.35300009325
5066
26301
200
text/css
Stylesheet
https://www.xdate.ch/build/app-md-up.css?v112
h2
425.17499998212
495.24200009182
5113
25457
200
text/css
Stylesheet
https://www.xdate.ch/build/app-lg-up.css?v112
h2
425.52099982277
507.19700008631
4860
24349
200
text/css
Stylesheet
https://www.xdate.ch/build/app-xl-up.css?v112
h2
425.67100003362
493.03899984807
4413
22472
200
text/css
Stylesheet
https://www.xdate.ch/img/bg_blur_1536x816.webp?v112
h2
433.02999995649
499.71600016579
33415
32986
200
image/webp
Image
https://www.xdate.ch/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
433.20300010964
478.04700024426
4321
12332
200
application/javascript
Script
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
h2
433.37700003758
517.2939999029
5518
13970
200
text/javascript
Script
https://www.xdate.ch/build/app-print.css?v112
h2
433.6140002124
616.09400017187
1068
1500
200
text/css
Stylesheet
data
451.46899996325
451.61100011319
0
403
200
image/jpeg
Image
data
451.7080001533
451.75800006837
0
465
200
image/jpeg
Image
data
451.82099984959
451.92599995062
0
485
200
image/jpeg
Image
data
452.00499985367
452.06299982965
0
437
200
image/jpeg
Image
data
452.14099995792
452.20900001004
0
437
200
image/jpeg
Image
data
452.31899991632
452.38499995321
0
464
200
image/jpeg
Image
data
452.45400024578
452.51999981701
0
427
200
image/jpeg
Image
data
452.61000003666
452.67400005832
0
508
200
image/jpeg
Image
data
452.75499997661
452.82599981874
0
414
200
image/jpeg
Image
data
452.90199993178
452.97100022435
0
476
200
image/jpeg
Image
data
453.03699979559
453.10699986294
0
509
200
image/jpeg
Image
data
453.18400021642
453.25399981812
0
448
200
image/jpeg
Image
data
453.35200009868
453.41899991035
0
416
200
image/jpeg
Image
data
453.49400024861
453.55900004506
0
460
200
image/jpeg
Image
data
453.65499984473
453.70900025591
0
507
200
image/jpeg
Image
data
453.76300020143
453.81599990651
0
452
200
image/jpeg
Image
data
453.87399988249
453.94300017506
0
519
200
image/jpeg
Image
data
454.01699980721
454.07199999318
0
482
200
image/jpeg
Image
data
454.13700025529
454.20200005174
0
418
200
image/jpeg
Image
data
454.2660000734
454.33499990031
0
428
200
image/jpeg
Image
data
454.39800014719
454.45600012317
0
480
200
image/jpeg
Image
data
454.51200008392
454.55999998376
0
425
200
image/jpeg
Image
data
454.61700018495
454.6730001457
0
492
200
image/jpeg
Image
data
455.47599997371
455.53399994969
0
477
200
image/jpeg
Image
data
455.60100022703
455.65300015733
0
450
200
image/jpeg
Image
data
455.71799995378
455.76900010929
0
478
200
image/jpeg
Image
data
455.81800024956
455.86499990895
0
453
200
image/jpeg
Image
data
455.91499982402
455.97200002521
0
487
200
image/jpeg
Image
data
456.02900022641
456.07799990103
0
473
200
image/jpeg
Image
data
456.12999983132
456.17499994114
0
447
200
image/jpeg
Image
https://www.xdate.ch/build/app.js?v112
h2
484.95199996978
530.5530000478
239742
814507
200
application/javascript
Script
https://www.xdate.ch/build/runtime.js?v112
h2
485.36399984732
540.37800012156
1232
1505
200
application/javascript
Script
data
557.16599989682
557.35700018704
0
3883
200
image/svg+xml
Image
data
558.80300002173
558.88799997047
0
881
200
image/svg+xml
Image
data
563.03199985996
563.19200014696
0
181
200
image/svg+xml
Image
data
565.13899983838
565.20699989051
0
313
200
image/svg+xml
Image
data
567.13199988008
567.19599990174
0
498
200
image/svg+xml
Image
data
568.05599993095
568.11500014737
0
398
200
image/svg+xml
Image
data
569.51300008222
569.5710000582
0
319
200
image/svg+xml
Image
data
570.4600000754
570.51300024614
0
286
200
image/svg+xml
Image
data
577.13600015268
577.1989999339
0
177
200
image/svg+xml
Image
data
578.33700021729
578.38999992236
0
174
200
image/svg+xml
Image
data
579.82600014657
579.88200010732
0
205
200
image/svg+xml
Image
data
581.40899986029
581.46800007671
0
272
200
image/svg+xml
Image
data
583.40300014243
583.59199995175
0
1836
200
image/svg+xml
Image
data
585.11199988425
585.20000008866
0
770
200
image/svg+xml
Image
https://fonts.gstatic.com/s/inter/v12/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
h2
586.41699980944
589.87999986857
38708
37780
200
font/woff2
Font
https://www.google-analytics.com/analytics.js
h2
771.51300013065
777.05000014976
20451
49672
200
text/javascript
Script
https://code.jquery.com/jquery-3.6.0.min.js
h2
772.20800006762
786.08400002122
31311
89501
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j97&a=2007717941&t=pageview&_s=1&dl=https%3A%2F%2Fwww.xdate.ch%2F&ul=en-us&de=UTF-8&dt=xdate.ch%20%E2%96%B7%20Das%20schweizer%20Sex%20und%20Erotik%20Inserate%20Portal.&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAAABAAAAAC~&jid=1093392912&gjid=730236986&cid=1570810224.1664534390&tid=UA-1143873-1&_gid=816860607.1664534390&_r=1&_slc=1&z=168055103
h2
804.34199981391
807.99800017849
613
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j97&tid=UA-1143873-1&cid=1570810224.1664534390&jid=1093392912&gjid=730236986&_gid=816860607.1664534390&_u=IEBAAAAAAAAAAC~&z=678184837
h2
821.51899999008
825.44500008225
683
1
200
text/plain
XHR
https://www.xdate.ch/uploads/banner.json?1664534389854
h2
928.17799979821
1058.2980001345
6050
18885
200
application/json
Fetch
data
957.68300024793
957.90799986571
0
44
200
image/webp
Image
data
958.02300004289
958.10399996117
0
286
200
image/jpeg
Image
data
968.47000019625
968.59600022435
0
82
200
image/webp
Image
data
968.70099985972
968.77699997276
0
90
200
image/webp
Image
data
968.86799996719
968.94499985501
0
38
200
image/webp
Image
https://images.xdate.ch/cache/insertion_topad_desktop/d8d78dd975ae57aadf86d33c2ed5acf00f2fbbe9/165864311962dce2af8d6c49.84747547.jpeg
h2
977.19299979508
1174.0350001492
26288
25699
200
image/jpeg
Image
https://images.xdate.ch/cache/insertion_teaser_sm/a484c741252ad005c70aaac5cf14bf5f1f127ce5/16644777986335ea66e8b308.24546315.jpg
h2
977.33000013977
1113.6719998904
13203
12614
200
image/jpeg
Image
https://www.xdate.ch/media/cache/resolve/insertion_teaser_sm/4a96bb705dfc25dd4f6378e4130a5ec7787b47a3/1663838103632c2797e97d22.26027063.jpg
http/1.1
977.79700020328
1135.7729998417
555
0
302
text/html
https://www.xdate.ch/cdn-cgi/rum?
h2
985.86199991405
1001.8350002356
407
0
200
text/plain
XHR
https://images.xdate.ch/cache/insertion_teaser_sm/4a96bb705dfc25dd4f6378e4130a5ec7787b47a3/1663838103632c2797e97d22.26027063.jpg
h2
1136.0860001296
1278.4319999628
14507
13918
200
image/jpeg
Image
https://images.xdate.ch/cache/insertion_teaser_sm/138c54e5f8b41309a64fd10ed2d345fbdd654a07/16611718216303786da1b308.08312617.jpeg
h2
1151.523000095
1298.1920000166
24954
24365
200
image/jpeg
Image
data
1289.3019998446
1289.4560000859
0
37
200
image/gif
Image
https://images.xdate.ch/cache/insertion_teaser_sm/e4f8684889eb8091bdc94d14d38bf18a5d43a599/bc6cf80252dd1ec0bec355e58cee62c7b1b08a93.jpeg
h2
1290.5120002106
1526.670999825
24863
24274
200
image/jpeg
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
416.058
14.167
440.84
18.372
480.972
5.427
538.806
8.749
547.567
147.774
702.616
66.843
776.098
9.55
789.968
15.524
808.037
12.83
825.028
136.978
970.271
8.148
988.517
6.553
1066.11
6.031
1149.817
8.564
1182.893
5.714
1288.81
8.751
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images — Potential savings of 6 KiB
Images can slow down the page's load time. Xdate.ch should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.xdate.ch/img/bg_blur_1536x816.webp?v112
32986
6339
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Xdate.ch should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Xdate.ch should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Xdate.ch should consider minifying JS files.
Reduce unused CSS — Potential savings of 53 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Xdate.ch should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.xdate.ch/build/app.css?v112
63627
54628
Efficiently encode images — Potential savings of 14 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://images.xdate.ch/cache/insertion_topad_desktop/d8d78dd975ae57aadf86d33c2ed5acf00f2fbbe9/165864311962dce2af8d6c49.84747547.jpeg
25699
5318
https://images.xdate.ch/cache/insertion_teaser_sm/e4f8684889eb8091bdc94d14d38bf18a5d43a599/bc6cf80252dd1ec0bec355e58cee62c7b1b08a93.jpeg
24274
4643
https://images.xdate.ch/cache/insertion_teaser_sm/138c54e5f8b41309a64fd10ed2d345fbdd654a07/16611718216303786da1b308.08312617.jpeg
24365
4213
Serve images in next-gen formats — Potential savings of 52 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://images.xdate.ch/cache/insertion_topad_desktop/d8d78dd975ae57aadf86d33c2ed5acf00f2fbbe9/165864311962dce2af8d6c49.84747547.jpeg
25699
16269.35
https://images.xdate.ch/cache/insertion_teaser_sm/138c54e5f8b41309a64fd10ed2d345fbdd654a07/16611718216303786da1b308.08312617.jpeg
24365
14275.8
https://images.xdate.ch/cache/insertion_teaser_sm/e4f8684889eb8091bdc94d14d38bf18a5d43a599/bc6cf80252dd1ec0bec355e58cee62c7b1b08a93.jpeg
24274
14195.05
https://images.xdate.ch/cache/insertion_teaser_sm/4a96bb705dfc25dd4f6378e4130a5ec7787b47a3/1663838103632c2797e97d22.26027063.jpg
13918
8471.05
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 350 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.xdate.ch/
354.3
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Xdate.ch should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://xdate.ch/
190
https://www.xdate.ch/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Xdate.ch should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 20 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.xdate.ch/build/app.js?v112
20724
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.xdate.ch/img/bg_blur_1536x816.webp?v112
0
Avoids enormous network payloads — Total size was 593 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.xdate.ch/build/app.js?v112
239742
https://www.xdate.ch/build/app.css?v112
63627
https://fonts.gstatic.com/s/inter/v12/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
38708
https://www.xdate.ch/
34756
https://www.xdate.ch/img/bg_blur_1536x816.webp?v112
33415
https://code.jquery.com/jquery-3.6.0.min.js
31311
https://images.xdate.ch/cache/insertion_topad_desktop/d8d78dd975ae57aadf86d33c2ed5acf00f2fbbe9/165864311962dce2af8d6c49.84747547.jpeg
26288
https://images.xdate.ch/cache/insertion_teaser_sm/138c54e5f8b41309a64fd10ed2d345fbdd654a07/16611718216303786da1b308.08312617.jpeg
24954
https://images.xdate.ch/cache/insertion_teaser_sm/e4f8684889eb8091bdc94d14d38bf18a5d43a599/bc6cf80252dd1ec0bec355e58cee62c7b1b08a93.jpeg
24863
https://www.google-analytics.com/analytics.js
20451
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Xdate.ch should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.xdate.ch/
620.486
10.228
0.966
https://www.xdate.ch/build/app.js?v112
214.361
138.974
11.882
Minimizes main-thread work — 1.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
293.437
Style & Layout
211.46
Rendering
207.472
Script Evaluation
198.795
Parse HTML & CSS
29.726
Script Parsing & Compilation
16.166
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 27 requests • 593 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
27
607544
Script
6
302575
Image
6
137230
Stylesheet
7
85583
Font
1
38708
Document
1
34756
Other
6
8692
Media
0
0
Third-party
7
98720
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
40144
0
31311
0
21064
0
5518
0
683
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00049532706961865
0.00012166886652151
4.9605562570561E-5
1.9088169478226E-5
1.556377940758E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.xdate.ch/
496
74
https://www.xdate.ch/build/app.js?v112
1467.0027275085
68
Avoid non-composited animations — 9 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xdate.ch on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.

Audits

First Meaningful Paint — 1.0 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 420 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Xdate.ch should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Inter:wght@400;600;700&display=swap
1436
230
https://www.xdate.ch/build/app.css?v112
63627
160
Reduce unused JavaScript — Potential savings of 166 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.xdate.ch/build/app.js?v112
239742
148979
https://code.jquery.com/jquery-3.6.0.min.js
31311
20828
Serve static assets with an efficient cache policy — 4 resources found
Xdate.ch can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.xdate.ch/img/bg_blur_1536x816.webp?v112
1200000
33415
https://www.google-analytics.com/analytics.js
7200000
20451
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
86400000
5518
https://www.xdate.ch/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
4321

Other

Avoid an excessive DOM size — 1,945 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
1945
Maximum DOM Depth
15
Maximum Child Elements
43
68

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of xdate.ch. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Xdate.ch may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
LI
AG

ARIA

ARIA IDs are not unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that xdate.ch should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.6.1
jQuery
3.6.0
Modernizr
3.6.0
core-js
core-js-global@3.22.8; core-js-global@3.9.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://xdate.ch/
Allowed

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.xdate.ch/build/app.js?v112
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for xdate.ch. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xdate.ch on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
67

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of xdate.ch. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xdate.ch on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 80
Performance 68
Accessibility 68
Best Practices 92
SEO 100
PWA 70
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.xdate.ch/
Updated: 30th September, 2022

0.86 seconds
First Contentful Paint (FCP)
95%
3%
2%

0.01 seconds
First Input Delay (FID)
97%
2%
1%

68

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for xdate.ch. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Xdate.ch should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Xdate.ch should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Xdate.ch should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Xdate.ch should consider minifying JS files.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 330 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.xdate.ch/
330.721
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Xdate.ch should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://xdate.ch/
630
https://www.xdate.ch/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Xdate.ch should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.xdate.ch/img/bg_blur.webp?v112
0
Avoids enormous network payloads — Total size was 551 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.xdate.ch/build/app.js?v112
239742
https://www.xdate.ch/build/app.css?v112
63627
https://images.xdate.ch/cache/insertion_topad/f888828b160e005210966d8559c7b2daaa3a8c74/1664451799633584d7046425.40751325.jpg
42947
https://fonts.gstatic.com/s/inter/v12/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
38708
https://www.xdate.ch/
34295
https://images.xdate.ch/cache/insertion_teaser/3f23e6455581759312704b908019705d11f191b2/166135752563064dd5a85007.98729430.jpg
32237
https://code.jquery.com/jquery-3.6.0.min.js
31311
https://www.google-analytics.com/analytics.js
20451
https://www.xdate.ch/img/bg_blur.webp?v112
18885
https://www.xdate.ch/uploads/banner.json?1664534413873
6050
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Xdate.ch should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.xdate.ch/
3539.032
39.544
6.48
https://www.xdate.ch/build/app.js?v112
1034.276
746.556
48.624
Unattributable
182.996
16.652
0.92
https://www.xdate.ch/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
158.564
102.204
2.628
https://www.google-analytics.com/analytics.js
156.144
140.336
3.7
https://code.jquery.com/jquery-3.6.0.min.js
75.832
61.224
6.768
https://www.xdate.ch/build/app.css?v112
54.304
0
0
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 24 requests • 551 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
24
564167
Script
6
302575
Image
4
94869
Stylesheet
7
85583
Font
1
38708
Document
1
34295
Other
5
8137
Media
0
0
Third-party
7
98720
Minimize third-party usage — Third-party code blocked the main thread for 90 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
21064
82.308
31311
9.46
40144
0
5518
0
683
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00015353393554687
3.7821451822917E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 9 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.xdate.ch/
1749
564
https://www.xdate.ch/build/app.js?v112
6360
396
https://www.xdate.ch/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
3689
143
https://www.google-analytics.com/analytics.js
4912
141
https://www.xdate.ch/
1654
95
https://code.jquery.com/jquery-3.6.0.min.js
5062
87
https://www.xdate.ch/
1560
77
https://www.xdate.ch/
630
59
https://www.xdate.ch/build/app.css?v112
2910
54
Avoid non-composited animations — 7 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xdate.ch on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://xdate.ch/
http/1.1
0
60.374999884516
384
0
301
text/plain
https://www.xdate.ch/
h2
60.895999893546
390.62700001523
34295
229270
200
text/html
Document
https://fonts.googleapis.com/css2?family=Inter:wght@400;600;700&display=swap
h2
409.65899988078
421.01299995556
1436
6846
200
text/css
Stylesheet
https://www.xdate.ch/build/app.css?v112
h2
409.88099994138
463.82199996151
63627
330163
200
text/css
Stylesheet
https://www.xdate.ch/img/bg_blur.webp?v112
h2
418.07699995115
447.05099985003
18885
18456
200
image/webp
Image
https://www.xdate.ch/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
418.3179999236
435.00999989919
4321
12332
200
application/javascript
Script
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
h2
418.40000008233
477.25500003435
5518
13970
200
text/javascript
Script
https://www.xdate.ch/build/app-sm-up.css?v112
h2
418.90199994668
458.57600006275
5066
26301
200
text/css
Stylesheet
https://www.xdate.ch/build/app-md-up.css?v112
h2
419.25000003539
459.45399999619
5113
25457
200
text/css
Stylesheet
https://www.xdate.ch/build/app-lg-up.css?v112
h2
419.50499988161
458.11400003731
4860
24349
200
text/css
Stylesheet
https://www.xdate.ch/build/app-xl-up.css?v112
h2
419.81599992141
457.04800006934
4413
22472
200
text/css
Stylesheet
https://www.xdate.ch/build/app-print.css?v112
h2
420.36599991843
451.26100000925
1068
1500
200
text/css
Stylesheet
data
440.53899985738
440.6729999464
0
389
200
image/jpeg
Image
data
440.81399985589
440.910999896
0
461
200
image/jpeg
Image
data
441.01399998181
441.10699999146
0
437
200
image/jpeg
Image
data
441.19399995543
441.2739998661
0
465
200
image/jpeg
Image
data
441.37099990621
441.5460000746
0
485
200
image/jpeg
Image
data
441.68599997647
441.76499987952
0
437
200
image/jpeg
Image
data
441.85599987395
441.94599986076
0
437
200
image/jpeg
Image
data
442.05199996941
442.13099987246
0
464
200
image/jpeg
Image
data
442.22799991257
442.35099991783
0
427
200
image/jpeg
Image
data
442.45400000364
442.54600000568
0
508
200
image/jpeg
Image
data
442.6299999468
442.69399996847
0
414
200
image/jpeg
Image
data
442.77399987914
442.85800005309
0
476
200
image/jpeg
Image
data
442.96599994414
443.06099996902
0
509
200
image/jpeg
Image
data
443.15099995583
443.23399988934
0
448
200
image/jpeg
Image
data
443.33899999037
443.40600003488
0
416
200
image/jpeg
Image
data
443.48599994555
443.56699986383
0
460
200
image/jpeg
Image
data
443.66799993441
443.74300003983
0
507
200
image/jpeg
Image
data
443.82699998096
443.91499995254
0
452
200
image/jpeg
Image
data
444.00399993174
444.09199990332
0
519
200
image/jpeg
Image
data
444.18499991298
444.25499998033
0
482
200
image/jpeg
Image
data
444.34099993668
444.42599988542
0
418
200
image/jpeg
Image
data
444.53199999407
444.61199990474
0
428
200
image/jpeg
Image
data
444.69600007869
444.77099995129
0
480
200
image/jpeg
Image
data
444.85899992287
444.95799997821
0
425
200
image/jpeg
Image
data
445.06200007163
445.14600001276
0
492
200
image/jpeg
Image
data
445.25299989618
445.33000001684
0
450
200
image/jpeg
Image
data
445.41499996558
445.48800005578
0
478
200
image/jpeg
Image
data
445.58100006543
445.65799995326
0
453
200
image/jpeg
Image
data
445.76100003906
445.83999994211
0
487
200
image/jpeg
Image
https://www.xdate.ch/build/app.js?v112
h2
460.82699997351
514.38299985602
239742
814507
200
application/javascript
Script
https://www.xdate.ch/build/runtime.js?v112
h2
462.09599985741
507.15399999171
1232
1505
200
application/javascript
Script
data
495.98399992101
496.11299997196
0
313
200
image/svg+xml
Image
data
499.78099996224
500.13599987142
0
3883
200
image/svg+xml
Image
data
502.92699993588
503.08299995959
0
316
200
image/svg+xml
Image
data
505.70999993943
505.86399994791
0
489
200
image/svg+xml
Image
data
508.48399987444
508.6729999166
0
890
200
image/svg+xml
Image
data
511.42899994738
511.61699998192
0
881
200
image/svg+xml
Image
data
515.79199987464
515.97899990156
0
799
200
image/svg+xml
Image
data
519.62599996477
519.77999997325
0
498
200
image/svg+xml
Image
data
522.1629999578
522.26800005883
0
319
200
image/svg+xml
Image
data
524.13600008003
524.27199995145
0
286
200
image/svg+xml
Image
data
526.62799996324
526.78299997933
0
398
200
image/svg+xml
Image
https://www.xdate.ch/build/images/ad_placeholder.b9c3c5d4.svg
h2
535.0309999194
566.11300003715
800
593
200
image/svg+xml
Image
data
539.84400001355
540.01799994148
0
177
200
image/svg+xml
Image
data
542.86699998192
543.06000005454
0
174
200
image/svg+xml
Image
data
546.68799997307
546.83899995871
0
205
200
image/svg+xml
Image
data
549.57799986005
549.70999993384
0
272
200
image/svg+xml
Image
data
553.47399995662
553.70899988338
0
1836
200
image/svg+xml
Image
data
556.69800005853
556.87500000931
0
770
200
image/svg+xml
Image
https://fonts.gstatic.com/s/inter/v12/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
h2
558.88499994762
564.50399989262
38708
37780
200
font/woff2
Font
https://www.google-analytics.com/analytics.js
h2
791.11399990506
796.37299990281
20451
49672
200
text/javascript
Script
https://code.jquery.com/jquery-3.6.0.min.js
h2
794.79700000957
809.86999999732
31311
89501
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j97&a=1320045492&t=pageview&_s=1&dl=https%3A%2F%2Fwww.xdate.ch%2F&ul=en-us&de=UTF-8&dt=xdate.ch%20%E2%96%B7%20Das%20schweizer%20Sex%20und%20Erotik%20Inserate%20Portal.&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAAABAAAAAC~&jid=924559205&gjid=764071592&cid=1531016604.1664534414&tid=UA-1143873-1&_gid=1341457455.1664534414&_r=1&_slc=1&z=958172211
h2
924.14600006305
929.37000002712
613
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j97&tid=UA-1143873-1&cid=1531016604.1664534414&jid=924559205&gjid=764071592&_gid=1341457455.1664534414&_u=IEBAAAAAAAAAAC~&z=1880161236
h2
955.81099996343
961.8869998958
683
1
200
text/plain
XHR
https://www.xdate.ch/uploads/banner.json?1664534413873
h2
1102.1739998832
1239.6980000194
6050
18885
200
application/json
Fetch
data
1151.3079998549
1151.5110000037
0
44
200
image/webp
Image
data
1151.6769998707
1151.7789999489
0
286
200
image/jpeg
Image
data
1167.6330000628
1167.7729999647
0
82
200
image/webp
Image
data
1167.9310000036
1168.0429999251
0
90
200
image/webp
Image
data
1168.1949999183
1168.3070000727
0
38
200
image/webp
Image
https://images.xdate.ch/cache/insertion_topad/f888828b160e005210966d8559c7b2daaa3a8c74/1664451799633584d7046425.40751325.jpg
h2
1177.2749999072
1214.3419999629
42947
42210
200
image/webp
Image
https://www.xdate.ch/cdn-cgi/rum?
h2
1182.7589999884
1200.9659998585
407
0
200
text/plain
XHR
https://images.xdate.ch/cache/insertion_teaser/3f23e6455581759312704b908019705d11f191b2/166135752563064dd5a85007.98729430.jpg
h2
3252.4379999377
3371.8210000079
32237
31648
200
image/jpeg
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
397.11
19.188
426.696
23.865
453.131
7.243
469.63
13.576
484.262
281.897
766.66
8.6
780.871
5.007
785.896
71.526
858.459
14.697
877.676
6.538
890.621
35.214
929.834
21.659
961.018
197.818
1158.882
7.653
1170.46
7.851
1217.761
8.734
1235.758
5.89
1243.889
5.616
1256.947
8.665
1850.281
5.166
3233.398
5.917
3250.332
7.359
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Time to Interactive — 6.3 s
The time taken for the page to become fully interactive.
Speed Index — 4.0 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 390 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 3.7 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 3.3 s
The time taken for the primary content of the page to be rendered.

Other

Efficiently encode images — Potential savings of 5 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://images.xdate.ch/cache/insertion_teaser/3f23e6455581759312704b908019705d11f191b2/166135752563064dd5a85007.98729430.jpg
31648
4846
Serve images in next-gen formats — Potential savings of 19 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://images.xdate.ch/cache/insertion_teaser/3f23e6455581759312704b908019705d11f191b2/166135752563064dd5a85007.98729430.jpg
31648
19317.1
Avoid serving legacy JavaScript to modern browsers — Potential savings of 20 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.xdate.ch/build/app.js?v112
20724
Serve static assets with an efficient cache policy — 4 resources found
Xdate.ch can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.xdate.ch/img/bg_blur.webp?v112
1200000
18885
https://www.google-analytics.com/analytics.js
7200000
20451
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
86400000
5518
https://www.xdate.ch/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
4321

Metrics

First Contentful Paint — 3.3 s
The time taken for the first image or text on the page to be rendered.

Audits

Max Potential First Input Delay — 400 ms
Users could experience a delay when interacting with the page.

Other

Eliminate render-blocking resources — Potential savings of 1,130 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Xdate.ch should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Inter:wght@400;600;700&display=swap
1436
780
https://www.xdate.ch/build/app.css?v112
63627
900
Reduce unused CSS — Potential savings of 53 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Xdate.ch should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.xdate.ch/build/app.css?v112
63627
54190
Reduce unused JavaScript — Potential savings of 166 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.xdate.ch/build/app.js?v112
239742
148979
https://code.jquery.com/jquery-3.6.0.min.js
31311
20828
Avoid an excessive DOM size — 1,941 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
1941
Maximum DOM Depth
15
Maximum Child Elements
43
Minimize main-thread work — 5.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
1448.772
Other
1440.952
Script Evaluation
1141.556
Rendering
1004.144
Parse HTML & CSS
180.244
Script Parsing & Compilation
71.248
First Contentful Paint (3G) — 6420 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
68

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of xdate.ch. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Xdate.ch may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
ZH
LI
AG

ARIA

ARIA IDs are not unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that xdate.ch should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.6.1
jQuery
3.6.0
Modernizr
3.6.0
core-js
core-js-global@3.22.8; core-js-global@3.9.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://xdate.ch/
Allowed

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.xdate.ch/build/app.js?v112
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for xdate.ch. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xdate.ch on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
70

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of xdate.ch. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of xdate.ch on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 104.18.168.23
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization: Cloudflare, Inc.
Country: US
City: wafangdian
State: VA
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 62/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 29th May, 2022
Valid To: 29th May, 2023
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 16259326147177988938728579939925315015
Serial Number (Hex): 0C3B6EABE24A25F6D1C9DD33ECA14DC7
Valid From: 29th May, 2024
Valid To: 29th May, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : May 29 01:11:52.116 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:E8:65:2F:DB:60:FE:08:28:54:EC:A2:
58:A2:AE:69:72:87:1A:97:16:17:82:4C:EB:04:BD:EC:
4D:9E:E5:AF:1D:02:20:1C:7F:7C:7D:39:EF:DE:52:65:
F8:08:C9:22:CE:52:67:40:64:33:3A:6E:FD:45:21:D9:
A6:F1:DB:FC:58:9D:4E
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : May 29 01:11:52.119 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:32:AE:74:06:3D:13:B8:AC:AF:86:BB:24:
00:4A:15:A0:F5:DA:0B:DD:38:28:BC:65:59:B6:1D:99:
FD:A6:6B:DF:02:21:00:BB:61:B2:4F:D6:BE:09:73:D8:
56:CF:58:0A:EF:95:90:F9:ED:B9:FE:A8:92:F6:C3:06:
35:FF:C4:17:9F:55:EC
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : May 29 01:11:52.178 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:9B:85:56:E6:02:07:EC:79:76:71:4A:
5D:89:7B:23:0A:B1:CD:5D:FB:4A:6B:EE:F4:D1:DE:D7:
7D:0A:7D:D4:E8:02:21:00:E0:02:28:4C:23:10:94:D9:
AA:E4:49:A8:93:A9:49:1F:75:65:8B:FC:5F:32:D4:FB:
F2:93:4A:B4:D2:F0:00:B8
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.xdate.ch
DNS:xdate.ch
DNS:sni.cloudflaressl.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 30th September, 2022
Content-Type: text/html; charset=UTF-8
Cache-Control: must-revalidate, no-cache, private
Expires: 30th September, 2022
Server: cloudflare
Connection: keep-alive
Age: 593
Set-Cookie: *
CF-Cache-Status: DYNAMIC
Strict-Transport-Security: max-age=2592000
Access-Control-Allow-Origin: *
CF-RAY: 752c56171c4c1865-EWR

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: micah.ns.cloudflare.com
pam.ns.cloudflare.com
Full Whois: Requests of this client are not permitted. Please use https://www.nic.ch/whois/ for queries.

Nameservers

Name IP Address
micah.ns.cloudflare.com 173.245.59.206
pam.ns.cloudflare.com 172.64.32.138
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
0/5
0/5
0/5
$1,000 USD 1/5
$3,019,035 USD 4/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
$275 USD 1/5

Sites hosted on the same IP address