Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

versus.com

versus.com is SSL secured

Free website and domain report on versus.com

Last Updated: 5th May, 2021 Update Now
Overview

Snoop Summary for versus.com

This is a free and comprehensive report about versus.com. Versus.com is hosted in United States on a server with an IP address of 108.61.12.218, where USD is the local currency and the local language is English. Versus.com is expected to earn an estimated $5,066 USD per day from advertising revenue. The sale of versus.com would possibly be worth $3,698,127 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Versus.com receives an estimated 544,086 unique visitors every day - an insane amount of traffic! This report was last updated 5th May, 2021.

About versus.com

Site Preview: versus.com versus.com
Title:
Description:
Keywords and Tags: popular, public information
Related Terms: jadakiss versus freestyle
Fav Icon:
Age: Over 30 years old
Domain Created: 10th September, 1993
Domain Updated: 20th April, 2021
Domain Expires: 9th September, 2021
Review

Snoop Score

4/5 (Excellent!)

Valuation

$3,698,127 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 4,049
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 69
Moz Page Authority: 52

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 544,086
Monthly Visitors: 16,560,264
Yearly Visitors: 198,591,390
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $5,066 USD
Monthly Revenue: $154,190 USD
Yearly Revenue: $1,849,059 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: versus.com 10
Domain Name: versus 6
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.03 seconds
Load Time Comparison: Faster than 77% of sites

PageSpeed Insights

Avg. (All Categories) 91
Performance 96
Accessibility 92
Best Practices 86
SEO 92
Progressive Web App 89
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://versus.com/en
Updated: 7th January, 2021

1.70 seconds
First Contentful Paint (FCP)
48%
44%
8%

0.01 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
96

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.9 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive versus.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://versus.com/
0
51.798999978928
235
0
301
text/html
https://versus.com/
52.364999981364
268.87299999362
245
0
302
text/html
https://versus.com/en
269.24699998926
485.31999997795
40984
191333
200
text/html
Document
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
500.0669999863
580.5859999964
1414
1843
200
text/css
Stylesheet
https://assets.versus.io/compiled/aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landing~mouch~55576cbb-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
500.18000000273
601.5400000033
4058
17633
200
text/css
Stylesheet
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
500.37699998938
589.74699999089
5549
30634
200
text/css
Stylesheet
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
500.55899997824
670.50799998106
53309
169145
200
application/javascript
Script
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~7c9a1a88-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
500.83299999824
633.62199999392
7319
19770
200
application/javascript
Script
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~639c254e-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
501.19099998847
646.29000000423
20317
63002
200
application/javascript
Script
https://assets.versus.io/compiled/vendors~blogpost~comparison~landing~moucho~oldToplist~property~toplist-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
501.31799999508
629.69000000157
1364
1595
200
application/javascript
Script
https://assets.versus.io/compiled/aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landing~mouch~55576cbb-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
501.4599999995
633.22299998254
14011
48317
200
application/javascript
Script
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
501.62799999816
716.8599999859
10080
30802
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
604.74799998337
609.19399998966
19452
47051
200
text/javascript
Script
https://versus.com/img/versus.svg
604.98999999254
628.98199999472
9931
9571
200
image/svg+xml
Image
https://images.versus.io/release/xiaomi-mi-11/release-1609730927243.variety.jpg
605.27999998885
688.60100000165
9227
8278
200
image/webp
Image
https://images.versus.io/release/realme-watch-s-pro/release-1609730807019.variety.jpg
605.41399999056
685.77799998457
9671
8722
200
image/webp
Image
https://images.versus.io/release/apple-airpods-max/release-1609730766299.variety.jpg
605.53499998059
710.17700000084
3916
2968
200
image/webp
Image
https://images.versus.io/release/nokia-5-4/release-1609730702172.variety.jpg
605.67499999888
690.38399998681
8663
7714
200
image/webp
Image
https://images.versus.io/release/zte-nubia-red-magic-cyberpods/release-1609730622843.variety.jpg
605.81399998046
680.86699998821
7877
6928
200
image/webp
Image
https://images.versus.io/release/amazfit-gts-2e/release-1609730534338.variety.jpg
605.91699997894
696.92799999029
8659
7710
200
image/webp
Image
https://images.versus.io/release/xiaomi-redmi-9-power/release-1609730419648.variety.jpg
606.13199998625
698.447999981
8453
7504
200
image/webp
Image
https://images.versus.io/release/oppo-reno5-pro-5g/release-1609730289638.variety.jpg
606.2769999844
688.14199999906
10225
9276
200
image/webp
Image
https://images.versus.io/release/xiaomi-mi-watch-lite/release-1609730219638.variety.jpg
606.41899998882
719.90199998254
6573
5624
200
image/webp
Image
https://images.versus.io/release/vivo-y52s/release-1609730135209.variety.jpg
606.5660000022
750.55799999973
7485
6536
200
image/webp
Image
https://i.ytimg.com/vi/WjHGRR69Nkc/mqdefault.jpg
606.66399999172
611.18300000089
17490
16983
200
image/jpeg
Image
https://i.ytimg.com/vi/ERQeu6Rb9W8/mqdefault.jpg
606.77399998531
621.80100000114
17745
17237
200
image/jpeg
Image
https://i.ytimg.com/vi/dHrc0PnJv78/mqdefault.jpg
606.88499998651
613.70099999476
20080
19314
200
image/jpeg
Image
https://i.ytimg.com/vi/zTdyrge9HHg/mqdefault.jpg
607.11099999025
614.07699997653
19346
18838
200
image/jpeg
Image
https://images.versus.io/landing/illustration_2.jpg
611.87699998845
693.09399998747
43797
42854
200
image/webp
Image
https://www.google-analytics.com/plugins/ua/ecommerce.js
745.95499999123
750.08100000559
1339
1403
200
text/javascript
Script
https://www.google-analytics.com/gtm/js?id=GTM-5BKKC83&cid=37774828.1610052771&aip=true
759.34599997709
781.90499998163
34091
84434
200
application/javascript
Script
https://static.chartbeat.com/js/chartbeat.js
819.41899997764
841.95400000317
14774
36363
200
application/x-javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j87&aip=1&a=1774946736&t=pageview&_s=1&dl=https%3A%2F%2Fversus.com%2Fen&ul=en-us&de=UTF-8&dt=Versus%20%7C%20Compare%20everything&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=aGBAAEITQAAAAC~&jid=369164773&gjid=167512562&cid=37774828.1610052771&tid=UA-20370356-4&_gid=866481347.1610052771&_r=1&_slc=1&cg1=Homepage&cg2=Homepage&cg3=no&z=1232993276
894.79399999254
897.9260000051
621
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j87&tid=UA-20370356-4&cid=37774828.1610052771&jid=369164773&gjid=167512562&_gid=866481347.1610052771&_u=aGBAAEISQAAAAC~&z=462828297
900.73299998767
903.7449999887
692
2
200
text/plain
XHR
https://ping.chartbeat.net/ping?h=versus.com&p=%2Fen&u=BR0B0kB0IN1-B3UrnU&d=versus.com&g=28270&g0=No%20Section&g1=No%20Author&n=1&f=00001&c=0&x=0&m=0&y=8754&o=1350&w=940&j=45&R=1&W=0&I=0&E=0&e=0&r=&b=819&t=CuTayBqLbukC1EeBiB_axP6qp_0S&V=121&i=Versus%20%7C%20Compare%20everything&tz=480&sn=1&sv=CWRkb9D2gk1PDBxRj7iQ3thTI-nu&sd=1&im=067b2ff3&_
933.74700000277
948.70899998932
250
43
200
image/gif
Image
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j87&tid=UA-20370356-4&cid=37774828.1610052771&jid=369164773&_u=aGBAAEISQAAAAC~&z=564240999
934.76999999257
944.42699998035
683
42
200
image/gif
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)
516.373
8.064
631.908
5.902
637.825
80.536
718.66
8.959
738.448
12.401
759.96
7.794
768.833
18.846
788.123
8.801
809.861
23.484
846.739
56.349
903.167
9.999
914.396
8.691
928.802
32.656
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 40 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Versus.com 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://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
1414
230
https://assets.versus.io/compiled/aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landing~mouch~55576cbb-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
4058
230
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
5549
270
Properly size images — Potential savings of 21 KiB
Images can slow down the page's load time. Versus.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://i.ytimg.com/vi/dHrc0PnJv78/mqdefault.jpg
19314
5694
https://i.ytimg.com/vi/zTdyrge9HHg/mqdefault.jpg
18838
5554
https://i.ytimg.com/vi/ERQeu6Rb9W8/mqdefault.jpg
17237
5082
https://i.ytimg.com/vi/WjHGRR69Nkc/mqdefault.jpg
16983
5007
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Versus.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Versus.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Versus.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Versus.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 45 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.google-analytics.com/gtm/js?id=GTM-5BKKC83&cid=37774828.1610052771&aip=true
34091
23657
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
53309
21946
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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 220 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://versus.com/en
217.071
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Versus.com 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 0 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://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~639c254e-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
59

Diagnostics

Avoids enormous network payloads — Total size was 430 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
53309
https://images.versus.io/landing/illustration_2.jpg
43797
https://versus.com/en
40984
https://www.google-analytics.com/gtm/js?id=GTM-5BKKC83&cid=37774828.1610052771&aip=true
34091
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~639c254e-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
20317
https://i.ytimg.com/vi/dHrc0PnJv78/mqdefault.jpg
20080
https://www.google-analytics.com/analytics.js
19452
https://i.ytimg.com/vi/zTdyrge9HHg/mqdefault.jpg
19346
https://i.ytimg.com/vi/ERQeu6Rb9W8/mqdefault.jpg
17745
https://i.ytimg.com/vi/WjHGRR69Nkc/mqdefault.jpg
17490
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Versus.com 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.1 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://versus.com/en
237.479
26.657
5.415
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
51.902
47.411
1.941
Minimizes main-thread work — 0.4 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)
Script Evaluation
137.447
Style & Layout
84.807
Rendering
79.912000000002
Other
73.188
Script Parsing & Compilation
23.5
Parse HTML & CSS
16.162
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 — 36 requests • 430 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
36
439925
Image
18
210071
Script
10
176056
Document
1
40984
Stylesheet
3
11021
Other
4
1793
Media
0
0
Font
0
0
Third-party
32
388530
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)
SHOW DETAILS
74661
0
SHOW DETAILS
55503
0
SHOW DETAILS
15024
0
SHOW DETAILS
692
0
SHOW DETAILS
683
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
div
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
versus logo
1.4639698800455E-5
div
6.8382208985949E-6
Type here to compare up to 7 items
5.5547394376279E-6
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

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.

Opportunities

Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Versus.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://versus.com/
190
https://versus.com/
150
https://versus.com/en
0

Diagnostics

Serve static assets with an efficient cache policy — 7 resources found
Versus.com 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://i.ytimg.com/vi/WjHGRR69Nkc/mqdefault.jpg
300000
17490
https://www.google-analytics.com/plugins/ua/ecommerce.js
3600000
1339
https://i.ytimg.com/vi/dHrc0PnJv78/mqdefault.jpg
7200000
20080
https://www.google-analytics.com/analytics.js
7200000
19452
https://i.ytimg.com/vi/zTdyrge9HHg/mqdefault.jpg
7200000
19346
https://i.ytimg.com/vi/ERQeu6Rb9W8/mqdefault.jpg
7200000
17745
https://static.chartbeat.com/js/chartbeat.js
7200000
14774
Avoid an excessive DOM size — 1,372 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
1,372
Maximum DOM Depth
SHOW DETAILS
15
Maximum Child Elements
SHOW DETAILS
10
92

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of versus.com. 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.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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.
`[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-*]` 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.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
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.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` 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.

Contrast

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

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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Versus.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Versus.com may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img

Navigation

Some elements have 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.
Failing Elements
Search Input
input

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.
86

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.

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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
3.6.4: global
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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://assets.versus.io/compiled/vendors~blogpost~comparison~landing~moucho~oldToplist~property~toplist-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/vendors~blogpost~comparison~landing~moucho~oldToplist~property~toplist-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~7c9a1a88-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~7c9a1a88-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~639c254e-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~639c254e-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map
https://assets.versus.io/compiled/aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landing~mouch~55576cbb-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landing~mouch~55576cbb-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map

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
http://versus.com/

Audits

Registers an `unload` listener
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.
URL
SHOW DETAILS
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for versus.com. 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 versus.com 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.
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.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img

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.
89

Progressive Web App

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.
Current page responds with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.

Installable

Registers 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.
Web app manifest meets the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
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 versus.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Fast and reliable

`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

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
http://versus.com/

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) 87
Performance 75
Accessibility 92
Best Practices 86
SEO 92
Progressive Web App 89
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://versus.com/en
Updated: 7th January, 2021

2.34 seconds
First Contentful Paint (FCP)
35%
50%
15%

0.04 seconds
First Input Delay (FID)
91%
7%
2%

Simulate loading on mobile
75

Performance

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

Metrics

Speed Index — 3.1 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Versus.com should consider serving more appropriate-sized images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Versus.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Versus.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Versus.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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 120 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://versus.com/en
122.034
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Versus.com 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 0 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://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~639c254e-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
59

Diagnostics

Avoids enormous network payloads — Total size was 408 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
53342
https://versus.com/en
41012
https://www.google-analytics.com/gtm/js?id=GTM-5BKKC83&cid=1463656312.1610052787&aip=true
34091
https://images.versus.io/landing/illustration_2_mobile.jpg
22002
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~639c254e-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
20246
https://i.ytimg.com/vi/dHrc0PnJv78/mqdefault.jpg
19822
https://www.google-analytics.com/analytics.js
19452
https://i.ytimg.com/vi/zTdyrge9HHg/mqdefault.jpg
19354
https://i.ytimg.com/vi/ERQeu6Rb9W8/mqdefault.jpg
17754
https://i.ytimg.com/vi/WjHGRR69Nkc/mqdefault.jpg
17498
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Versus.com 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.
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 — 36 requests • 408 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
36
417902
Image
18
188043
Script
10
176026
Document
1
41012
Stylesheet
3
11021
Other
4
1800
Media
0
0
Font
0
0
Third-party
32
366472
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
div
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
input
0.001164306640625
div
0.00065139431423611
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 — 11 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://versus.com/en
1598
485
https://static.chartbeat.com/js/chartbeat.js
5709
261
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
5359
237
https://versus.com/en
2190
219
https://www.google-analytics.com/analytics.js
4050
123
https://www.google-analytics.com/gtm/js?id=GTM-5BKKC83&cid=1463656312.1610052787&aip=true
5596
113
https://versus.com/en
2083
81
https://versus.com/en
630
67
https://versus.com/en
1537
61
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
697
59
https://versus.com/en
1440
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

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.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://versus.com/
0
42.891999706626
250
0
301
text/html
https://versus.com/
43.599999975413
75.072999577969
237
0
302
text/html
https://versus.com/en
75.763999950141
196.80199958384
41012
191333
200
text/html
Document
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
220.92100000009
244.83799980953
1414
1843
200
text/css
Stylesheet
https://assets.versus.io/compiled/aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landing~mouch~55576cbb-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
221.3169997558
272.93999958783
4058
17633
200
text/css
Stylesheet
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
221.5319997631
273.21699960157
5549
30634
200
text/css
Stylesheet
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
222.02700003982
327.22699968144
53342
169145
200
application/javascript
Script
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~7c9a1a88-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
222.429999616
301.31999962032
7327
19770
200
application/javascript
Script
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~639c254e-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
223.9830000326
319.20399982482
20246
63002
200
application/javascript
Script
https://assets.versus.io/compiled/vendors~blogpost~comparison~landing~moucho~oldToplist~property~toplist-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
225.76399985701
296.04799998924
1364
1595
200
application/javascript
Script
https://assets.versus.io/compiled/aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landing~mouch~55576cbb-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
226.38199990615
345.14599991962
14011
48317
200
application/javascript
Script
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
226.86199983582
296.95099964738
10080
30802
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
280.48299998045
286.25799994916
19452
47051
200
text/javascript
Script
https://versus.com/img/versus.svg
280.89299984276
311.10499985516
9931
9571
200
image/svg+xml
Image
https://images.versus.io/release/xiaomi-mi-11/release-1609730927243.variety.jpg
281.15499997512
305.74599979445
9227
8278
200
image/webp
Image
https://images.versus.io/release/realme-watch-s-pro/release-1609730807019.variety.jpg
281.78799990565
320.06999989972
9671
8722
200
image/webp
Image
https://images.versus.io/release/apple-airpods-max/release-1609730766299.variety.jpg
282.0679997094
309.71699999645
3916
2968
200
image/webp
Image
https://images.versus.io/release/nokia-5-4/release-1609730702172.variety.jpg
282.32300002128
304.13599964231
8663
7714
200
image/webp
Image
https://images.versus.io/release/zte-nubia-red-magic-cyberpods/release-1609730622843.variety.jpg
282.73099986836
306.56299972907
7877
6928
200
image/webp
Image
https://images.versus.io/release/amazfit-gts-2e/release-1609730534338.variety.jpg
282.98099990934
313.56399971992
8659
7710
200
image/webp
Image
https://images.versus.io/release/xiaomi-redmi-9-power/release-1609730419648.variety.jpg
283.25599990785
310.74499990791
8453
7504
200
image/webp
Image
https://images.versus.io/release/oppo-reno5-pro-5g/release-1609730289638.variety.jpg
283.48899958655
332.26799964905
10225
9276
200
image/webp
Image
https://images.versus.io/release/xiaomi-mi-watch-lite/release-1609730219638.variety.jpg
283.71199965477
309.46599971503
6573
5624
200
image/webp
Image
https://images.versus.io/release/vivo-y52s/release-1609730135209.variety.jpg
284.08299991861
309.58599969745
7485
6536
200
image/webp
Image
https://i.ytimg.com/vi/WjHGRR69Nkc/mqdefault.jpg
284.32099986821
292.13199997321
17498
16983
200
image/jpeg
Image
https://i.ytimg.com/vi/ERQeu6Rb9W8/mqdefault.jpg
284.49899982661
290.93399969861
17754
17237
200
image/jpeg
Image
https://i.ytimg.com/vi/dHrc0PnJv78/mqdefault.jpg
284.66099966317
291.37599980459
19822
19314
200
image/jpeg
Image
https://i.ytimg.com/vi/zTdyrge9HHg/mqdefault.jpg
284.89199979231
290.00299982727
19354
18838
200
image/jpeg
Image
https://images.versus.io/landing/illustration_2_mobile.jpg
298.56499982998
320.28099987656
22002
21094
200
image/webp
Image
https://www.google-analytics.com/plugins/ua/ecommerce.js
652.74599986151
657.53099974245
1339
1403
200
text/javascript
Script
https://www.google-analytics.com/gtm/js?id=GTM-5BKKC83&cid=1463656312.1610052787&aip=true
675.11900002137
704.04999982566
34091
84434
200
application/javascript
Script
https://static.chartbeat.com/js/chartbeat.js
801.42399994656
837.86699967459
14774
36363
200
application/x-javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j87&aip=1&a=219958196&t=pageview&_s=1&dl=https%3A%2F%2Fversus.com%2Fen&ul=en-us&de=UTF-8&dt=Versus%20%7C%20Compare%20everything&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=aGBAAEITQAAAAC~&jid=412799198&gjid=957025596&cid=1463656312.1610052787&tid=UA-20370356-4&_gid=64437874.1610052787&_r=1&_slc=1&cg1=Homepage&cg2=Homepage&cg3=no&z=138183840
967.62799983844
972.41599997506
621
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j87&tid=UA-20370356-4&cid=1463656312.1610052787&jid=412799198&gjid=957025596&_gid=64437874.1610052787&_u=aGBAAEISQAAAAC~&z=148469586
984.21899974346
988.25599998236
692
2
200
text/plain
XHR
https://ping.chartbeat.net/ping?h=versus.com&p=%2Fen&u=BjL7WID8oAnKC6mnjI&d=versus.com&g=28270&g0=No%20Section&g1=No%20Author&n=1&f=00001&c=0&x=0&m=0&y=10656&o=360&w=640&j=45&R=1&W=0&I=0&E=0&e=0&r=&b=804&t=JyskIBu0b01Bhx9qqeBPuMBm_P2&V=121&i=Versus%20%7C%20Compare%20everything&tz=480&sn=1&sv=BeORoqBnRkUuDGCWfSJ6dT1BHoP-K&sd=1&im=067b2ff3&_
1059.9940000102
1076.3189997524
250
43
200
image/gif
Image
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j87&tid=UA-20370356-4&cid=1463656312.1610052787&jid=412799198&_u=aGBAAEISQAAAAC~&z=522171997
1060.870999936
1067.7859997377
683
42
200
image/gif
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)
253.548
12.511
271.982
11.699
331.17
15.245
346.435
242.628
594.588
20.26
632.379
33.272
672.967
5.519
682.135
14.679
696.859
30.651
729.858
13.086
748.944
54.65
804.767
14.274
821.939
8.46
830.759
12.358
843.162
9.079
852.279
118.746
971.069
20.365
991.448
28.274
1026.563
6.119
1038.636
5.037
1043.83
65.331
1117.291
10.036
1128.661
5.002
1135.897
8.693
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 3.1 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 5.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 300 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).

Other

First CPU Idle — 4.4 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 3.1 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 60 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive versus.com as laggy when the latency is higher than 0.05 seconds.

Opportunities

Eliminate render-blocking resources — Potential savings of 150 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Versus.com 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://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
1414
780
https://assets.versus.io/compiled/aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landing~mouch~55576cbb-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
4058
930
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.css
5549
930
Defer offscreen images — Potential savings of 80 KiB
Time to Interactive can be slowed down by resources on the page. Versus.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://i.ytimg.com/vi/dHrc0PnJv78/mqdefault.jpg
19314
19314
https://i.ytimg.com/vi/zTdyrge9HHg/mqdefault.jpg
18838
18838
https://images.versus.io/release/oppo-reno5-pro-5g/release-1609730289638.variety.jpg
9276
9276
https://images.versus.io/release/amazfit-gts-2e/release-1609730534338.variety.jpg
7710
7710
https://images.versus.io/release/xiaomi-redmi-9-power/release-1609730419648.variety.jpg
7504
7504
https://images.versus.io/release/zte-nubia-red-magic-cyberpods/release-1609730622843.variety.jpg
6928
6928
https://images.versus.io/release/vivo-y52s/release-1609730135209.variety.jpg
6536
6536
https://images.versus.io/release/xiaomi-mi-watch-lite/release-1609730219638.variety.jpg
5624
5624
Remove unused JavaScript — Potential savings of 45 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.google-analytics.com/gtm/js?id=GTM-5BKKC83&cid=1463656312.1610052787&aip=true
34091
23657
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
53342
21959

Diagnostics

Serve static assets with an efficient cache policy — 8 resources found
Versus.com 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://images.versus.io/landing/illustration_2_mobile.jpg
0
22002
https://i.ytimg.com/vi/WjHGRR69Nkc/mqdefault.jpg
300000
17498
https://www.google-analytics.com/plugins/ua/ecommerce.js
3600000
1339
https://i.ytimg.com/vi/dHrc0PnJv78/mqdefault.jpg
7200000
19822
https://www.google-analytics.com/analytics.js
7200000
19452
https://i.ytimg.com/vi/zTdyrge9HHg/mqdefault.jpg
7200000
19354
https://i.ytimg.com/vi/ERQeu6Rb9W8/mqdefault.jpg
7200000
17754
https://static.chartbeat.com/js/chartbeat.js
7200000
14774
Avoid an excessive DOM size — 1,372 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
1,372
Maximum DOM Depth
SHOW DETAILS
15
Maximum Child Elements
SHOW DETAILS
10
Reduce JavaScript execution time — 1.3 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://versus.com/en
2014.76
241.556
52.244
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
425.8
399.024
8.16
Unattributable
299.66
5.66
1.208
https://static.chartbeat.com/js/chartbeat.js
268.292
256.672
4.996
https://www.google-analytics.com/gtm/js?id=GTM-5BKKC83&cid=1463656312.1610052787&aip=true
186.912
162.656
18.232
https://www.google-analytics.com/analytics.js
145.64
115.704
6.188
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
62.116
2.464
50.992
Minimize main-thread work — 3.5 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)
Script Evaluation
1185.496
Style & Layout
951.888
Rendering
500.35999999999
Other
469.204
Script Parsing & Compilation
178.4
Parse HTML & CSS
158.972
Garbage Collection
39.712

Metrics

Largest Contentful Paint — 4.1 s
The timing of the largest text or image that is painted.

Other

Max Potential First Input Delay — 260 ms
Users could experience a delay when interacting with the page.
First Contentful Paint (3G) — 6720 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Versus.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://versus.com/
630
https://versus.com/
480
https://versus.com/en
0

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 320 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)
SHOW DETAILS
15024
198.672
SHOW DETAILS
55503
120.44
SHOW DETAILS
74428
0
SHOW DETAILS
692
0
SHOW DETAILS
683
0
92

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of versus.com. 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.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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.
`[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-*]` 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.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
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.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` 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.

Contrast

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

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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Versus.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Versus.com may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img

Navigation

Some elements have 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.
Failing Elements
Search Input
input

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.
86

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.

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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
3.6.4: global
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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://assets.versus.io/compiled/vendors~blogpost~comparison~landing~moucho~oldToplist~property~toplist-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/vendors~blogpost~comparison~landing~moucho~oldToplist~property~toplist-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~7c9a1a88-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~7c9a1a88-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~639c254e-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~639c254e-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/vendors~aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landi~3b1cb499-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/landing-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map
https://assets.versus.io/compiled/aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landing~mouch~55576cbb-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs
https://assets.versus.io/compiled/aboutUs~authorPage~authors~blogpost~categories~comparison~editorialGuidelines~glossary~landing~mouch~55576cbb-7904c9a42f0aa1d213e7211752df3b4ed923b2a2.min.mjs.map

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
http://versus.com/

Audits

Registers an `unload` listener
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.
URL
SHOW DETAILS
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for versus.com. 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 versus.com 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
SHOW DETAILS
100.00%
≥ 12px

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.
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.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img

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.
89

Progressive Web App

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.
Current page responds with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.

Installable

Registers 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.
Web app manifest meets the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
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 versus.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Fast and reliable

`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

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
http://versus.com/

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: 108.61.12.218
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
URGE IO GmbH
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
united domains AG 89.31.137.221
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 89/100
WOT Child Safety: 88/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: versus.com
Issued By: R3
Valid From: 6th April, 2021
Valid To: 5th July, 2021
Subject: CN = versus.com
Hash: 67c2053b
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04D590E6C86D0EF2E92CCBEFAC3AF722F8FB
Serial Number (Hex): 04D590E6C86D0EF2E92CCBEFAC3AF722F8FB
Valid From: 6th April, 2024
Valid To: 5th July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org
Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/
SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Apr 7 00:47:39.125 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:30:51:5E:3D:7F:57:8C:2F:9C:F9:44:DF:
1E:37:40:3F:7C:ED:4A:9B:A9:F3:D4:73:F9:59:9D:B5:
7E:D1:DF:F8:02:20:03:35:8E:27:3F:04:4E:F0:8A:C0:
D1:FA:A5:35:19:4A:40:04:A2:01:62:80:FA:AA:7A:88:
1C:60:43:15:FB:C8
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Apr 7 00:47:39.164 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:A1:3C:ED:33:71:8A:13:D1:18:D7:4A:
DC:C4:81:6C:BA:41:1C:7C:F5:F4:63:22:74:6E:2D:1B:
23:19:40:55:93:02:21:00:C6:71:C3:F4:82:71:3F:5B:
D6:28:57:24:21:9B:77:8B:1D:82:9B:0B:D4:2F:E8:72:
68:5B:E7:CA:6D:A7:C4:E1
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.versus.com
DNS:versus.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
versus.com. 108.61.12.218 IN 59

NS Records

Host Nameserver Class TTL
versus.com. ns-1040.awsdns-02.org. IN 21599
versus.com. ns-1869.awsdns-41.co.uk. IN 21599
versus.com. ns-398.awsdns-49.com. IN 21599
versus.com. ns-668.awsdns-19.net. IN 21599

MX Records

Priority Host Server Class TTL
1 versus.com. aspmx.l.google.com. IN 299
10 versus.com. aspmx2.googlemail.com. IN 299
10 versus.com. aspmx3.googlemail.com. IN 299
5 versus.com. alt1.aspmx.l.google.com. IN 299
5 versus.com. alt2.aspmx.l.google.com. IN 299

SOA Records

Domain Name Primary NS Responsible Email TTL
versus.com. ns-398.awsdns-49.com. awsdns-hostmaster.amazon.com. 899

TXT Records

Host Value Class TTL
versus.com. v=spf1 IN 299

HTTP Response Headers

Whois Lookup

Created: 10th September, 1993
Changed: 20th April, 2021
Expires: 9th September, 2021
Registrar: united domains AG
Status: clientTransferProhibited
Nameservers: ns-1040.awsdns-02.org
ns-1869.awsdns-41.co.uk
ns-398.awsdns-49.com
ns-668.awsdns-19.net
Owner State: DE
Owner Country: DE
Owner Email: https://www.united-domains.de/domain-inhaber-kontaktieren
Admin Email: https://www.united-domains.de/domain-inhaber-kontaktieren
Tech Email: https://www.united-domains.de/domain-inhaber-kontaktieren
Full Whois:
Domain Name: versus.com
Registry Domain ID: 1610685_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.udag.net
Registrar URL: https://www.united-domains.de/
Updated Date: 2021-04-20T14:55:47Z
Creation Date: 1993-09-10T04:00:00Z
Registrar Registration Expiration Date: 2021-09-09T04:00:00Z
Registrar: united domains AG
Registrar IANA ID: 1408
Registrar Abuse Contact Email: abuse@united-domains.de
Registrar Abuse Contact Phone: +49.8151368670
Reseller:
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name:
Registrant Street:
Registrant City:
Registrant State/Province: DE
Registrant Postal Code:
Registrant Country: DE
Registrant Phone:
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: https://www.united-domains.de/domain-inhaber-kontaktieren
Registry Admin ID:
Admin Name:
Admin Street:
Admin City:
Admin State/Province:
Admin Postal Code:
Admin Country:
Admin Phone:
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: https://www.united-domains.de/domain-inhaber-kontaktieren
Registry Tech ID:
Tech Name:
Tech Street:
Tech City:
Tech State/Province:
Tech Postal Code:
Tech Country:
Tech Phone:
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: https://www.united-domains.de/domain-inhaber-kontaktieren
Name Server: ns-398.awsdns-49.com
Name Server: ns-1040.awsdns-02.org
Name Server: ns-1869.awsdns-41.co.uk
Name Server: ns-668.awsdns-19.net
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-04-20T14:55:47Z <<<

For more information on Whois status codes, please visit https://www.icann.org/epp

WHOIS data will not be displayed due to privacy legislation. Please contact united-domains AG at whois@united-domains.de if you have legitimate interest to contact the registrant of the record.

; Whois Server Version 2.05
;
; Terms and conditions:
;
; This data is provided by united-domains AG
; for information purposes, and to assist persons obtaining information
; about or related to domain name registration records.
; united-domains AG does not guarantee its accuracy.
; By submitting a WHOIS query, you agree that you will use this data
; only for lawful purposes and that, under no circumstances, you will
; use this data to
; 1) allow, enable, or otherwise support the transmission of mass
; unsolicited, commercial advertising or solicitations via e-mail
; (spam); or
; 2) enable high volume, automated, electronic processes that apply
; to this WHOIS server.
; These terms may be changed without prior notice.
; By submitting this query, you agree to abide by this policy.

View Raw Whois

Nameservers

Name IP Address
ns-1040.awsdns-02.org 205.251.196.16
ns-1869.awsdns-41.co.uk 205.251.199.77
ns-398.awsdns-49.com 205.251.193.142
ns-668.awsdns-19.net 205.251.194.156
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
steephill.tv
$8,829 USD 2/5
takebackthetour.com
0/5
texags.com
$28,905 USD 2/5
thetennischannel.com
$10 USD
tsn.ca
$1,585,517 USD 4/5
All sites similar to versus.com

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
versus.beer
0/5
versus.bg
0/5
versus.com.pt
0/5
versus.gr
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
col3negtop.co.uk
0/5
kindred-fitness.com
0/5
submissionurl.com
$3,206 USD 2/5
vinsaara.info
$694 USD 1/5
Love W3 Snoop?
Update Now

versus.com Infographic

versus.com by the numbers infographic

Recently Updated

fotokid.net
vimeocdn.com
lolihub.com
politikfilm.net
tamilrockers.com
freean.us
ebravo.com
holyangelschool.org
themilionpixel.com
wapkiz.com

Recently Viewed

thecityoflights.net
cosmeticare.com
szbbw.net
svcic.com
tvdir.net
fgbss.com
aaaacccc.com
l-eco.fr
cloudq.net
csengineermag.com