Play competitive skill-based games and win real money

Overview

Snoop Summary for win.com

This is a free and comprehensive report about win.com. Win.com is hosted in United States on a server with an IP address of 172.67.196.110, where USD is the local currency and the local language is English. Win.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If win.com was to be sold it would possibly be worth $964 USD (based on the daily revenue potential of the website over a 24 month period). Win.com is somewhat popular with an estimated 458 daily unique visitors. This report was last updated 2nd April, 2021.

About win.com

Site Preview:
Title:	Play competitive skill-based games and win real money \| win.com
Description:	Win.com is an innovative gaming platform where you can beat the competition to win real money or simply play for fun. Enjoy a wide variety of games that can be played cross platform from anywhere, anytime.
Keywords and Tags:	gambling related
Related Terms:	enter free to win competitions, ves masine win win, win 4d, win blu rays, win cash, win dvds, win fabulous prizes, win job center, win win sokovnici, win win sporeti
Fav Icon:
Age:	Over 25 years old
Domain Created:	17th February, 1999
Domain Updated:	13th August, 2020
Domain Expires:	17th February, 2029

Review

Snoop Score

2/5

Valuation

$964 USD

Note: All valuation figures are estimates.

Popularity

Low

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	1,845,467
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority:	0
Moz Page Authority:	0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors:	458
Monthly Visitors:	13,951
Yearly Visitors:	167,305

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$1 USD
Monthly Revenue:	$40 USD
Yearly Revenue:	$477 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	win.com	7
Domain Name:	win	3
Extension (TLD):	com	3

Expiry Check:

Page Speed Analysis

Average Load Time:	1.37 seconds
Load Time Comparison:	Faster than 58% of sites

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on desktop

Performance

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

Metrics

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

Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.

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

Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.

Total Blocking Time — 40 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.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.0 s
The time taken for the page's main thread to be quiet enough to handle input.

First Meaningful Paint — 0.6 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 win.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	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://win.com/	http/1.1	0	76.460999902338	732	0	301
https://win.com/	h2	77.116000000387	224.94600014761	3841	11714	200	text/html	Document
https://win.com/_next/static/css/b520b97beea00891a34d.css	h2	239.72300020978	397.2340002656	1326	1106	200	text/css	Stylesheet
https://win.com/_next/static/css/cb825e7373893b3cde9c.css	h2	239.93600020185	316.1760000512	4951	33106	200	text/css	Stylesheet
https://win.com/_next/static/chunks/main-6957307470fcc6d1f962.js	h2	240.22699985653	409.00600003079	7650	20082	200	application/javascript	Script
https://win.com/_next/static/chunks/webpack-e067438c4cf4ef2ef178.js	h2	240.44700013474	547.34499985352	1759	1539	200	application/javascript	Script
https://win.com/_next/static/chunks/framework.628343e33877aa8e8b0a.js	h2	240.67700002342	553.41499997303	39539	133948	200	application/javascript	Script
https://win.com/_next/static/chunks/commons.cb82874e43d6dd0d0fae.js	h2	241.10700003803	305.29000004753	11194	32274	200	application/javascript	Script
https://win.com/_next/static/chunks/pages/_app-1925032a5b2cc966bdf2.js	h2	241.64600018412	489.71199989319	3360	7085	200	application/javascript	Script
https://win.com/_next/static/chunks/05d954cf.b5067be4255f49b388da.js	h2	241.85100011528	292.23400028422	22766	74569	200	application/javascript	Script
https://win.com/_next/static/chunks/ea88be26.180b1a26a0b09fc22697.js	h2	242.26800026372	679.92699984461	62127	261639	200	application/javascript	Script
https://win.com/_next/static/chunks/pages/index-fbf05be1e954ee3330b2.js	h2	242.50600021333	326.77899999544	55512	194512	200	application/javascript	Script
https://win.com/images/bg-textures.svg	h2	399.92600027472	539.75700028241	1692	1741	200	image/svg+xml	Image
https://win.com/images/win-logo.svg	h2	400.31199995428	600.38000019267	2711	4410	200	image/svg+xml	Image
https://win.com/animations/main-rocket-cover.svg	h2	400.54199984297	643.23800010607	6070	19248	200	image/svg+xml	Image
https://win.com/animations/pink-rocket-cover.svg	h2	400.69299982861	646.78299985826	10035	66097	200	image/svg+xml	Image
https://win.com/animations/scoreboard-cover.svg	h2	400.86300019175	681.13199993968	26753	70806	200	image/svg+xml	Image
https://win.com/images/play-skill-based-game.svg	h2	401.19200013578	591.89900010824	4153	8440	200	image/svg+xml	Image
https://win.com/images/have-fun-with-friends.svg	h2	401.62800019607	645.71700012311	4516	8548	200	image/svg+xml	Image
https://win.com/images/win-crypto.svg	h2	401.85200003907	615.33700022846	5189	10574	200	image/svg+xml	Image
https://win.com/images/social-media/email.svg	h2	402.01300010085	601.57700022683	1790	1419	200	image/svg+xml	Image
https://win.com/_next/static/teTf6P54em6UBW92wJ1G6/_buildManifest.js	h2	402.25900011137	541.62700008601	1293	464	200	application/javascript	Script
https://win.com/_next/static/teTf6P54em6UBW92wJ1G6/_ssgManifest.js	h2	402.4530001916	500.26299990714	1103	76	200	application/javascript	Script
https://win.com/fonts/Manrope-ExtraBold.ttf	h2	407.56299998611	665.84799997509	38727	93144	200	font/ttf	Font
https://win.com/fonts/Manrope-Regular.ttf	h2	407.81900007278	714.83700023964	39925	92376	200	font/ttf	Font
https://win.com/_next/static/css/cb825e7373893b3cde9c.css	h2	724.87800009549	800.96800019965	4943	33106	200	text/css	Fetch
https://widget.intercom.io/widget/zwq8jrz5	http/1.1	725.75600026175	773.78700021654	435	0	302
https://js.intercomcdn.com/shim.latest.js	h2	774.14599992335	790.36800004542	6267	16915	200	application/javascript	Script
https://js.intercomcdn.com/frame-modern.13f9a2c8.js	h2	812.9819999449	869.25600003451	69009	254598	200	application/javascript	Script
https://js.intercomcdn.com/vendor-modern.39db44f0.js	h2	813.44299996272	879.79099992663	38902	126410	200	application/javascript	Script
https://win.com/_next/static/chunks/05d954cf.b5067be4255f49b388da.js	h2	987.64500021935	1021.2550000288	22768	0	200	application/javascript	Other
https://win.com/_next/static/chunks/ea88be26.180b1a26a0b09fc22697.js	h2	987.98400023952	1099.3520002812	62128	0	200	application/javascript	Other
https://win.com/_next/static/css/cb825e7373893b3cde9c.css	h2	988.23100002483	1022.1609999426	4943	0	200	text/css	Other
https://win.com/_next/static/chunks/pages/index-fbf05be1e954ee3330b2.js	h2	990.0759998709	1033.6609999649	55506	0	200	application/javascript	Other
https://api-iam.intercom.io/messenger/web/ping	h2	1082.5340002775	1472.6169998758	2246	2928	200	application/json	XHR

Show Details

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)
260.872	9.902
435.475	21.249
464.149	6.734
595.977	23.983
626.006	5.616
676.809	6.85
695.028	9.244
708.89	10.301
721.851	8.162
735.425	9.778
746.094	8.095
755.018	7.302
762.37	5.492
824.947	21.513
851.221	146.358
997.725	14.861
1016.709	5.038
1022.671	6.017
1030.035	88.862
1121.851	9.403
1506.067	22.976

Show Details

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
Resources, such as JavaScript and style sheets, can block the first paint of the page. Win.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

Properly size images
Images can slow down the page's load time. Win.com should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Win.com should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Win.com should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Win.com should consider minifying JS files.

Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Win.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 120 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://win.com/_next/static/chunks/ea88be26.180b1a26a0b09fc22697.js	62127	54412
https://js.intercomcdn.com/frame-modern.13f9a2c8.js	69009	36889
https://win.com/_next/static/chunks/pages/index-fbf05be1e954ee3330b2.js	55512	31235

Show Details

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 150 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://win.com/	148.826

Show Details

Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Win.com should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
http://win.com/	190
https://win.com/	0

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Win.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://js.intercomcdn.com/vendor-modern.39db44f0.js	104
https://win.com/_next/static/chunks/pages/index-fbf05be1e954ee3330b2.js	77
https://win.com/_next/static/chunks/commons.cb82874e43d6dd0d0fae.js	58

Show Details

Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 611 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
https://js.intercomcdn.com/frame-modern.13f9a2c8.js	69009
https://win.com/_next/static/chunks/ea88be26.180b1a26a0b09fc22697.js	62128
https://win.com/_next/static/chunks/ea88be26.180b1a26a0b09fc22697.js	62127
https://win.com/_next/static/chunks/pages/index-fbf05be1e954ee3330b2.js	55512
https://win.com/_next/static/chunks/pages/index-fbf05be1e954ee3330b2.js	55506
https://win.com/fonts/Manrope-Regular.ttf	39925
https://win.com/_next/static/chunks/framework.628343e33877aa8e8b0a.js	39539
https://js.intercomcdn.com/vendor-modern.39db44f0.js	38902
https://win.com/fonts/Manrope-ExtraBold.ttf	38727
https://win.com/animations/scoreboard-cover.svg	26753

Show Details

Uses efficient cache policy on static assets — 1 resource found
Win.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://js.intercomcdn.com/shim.latest.js	300000	6267

Show Details

Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Win.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 — 4 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

Name	Type	Start Time (Ms)	Duration (Ms)
Next.js-before-hydration	Measure	0	863.715
Next.js-hydration	Measure	863.715	58.805
beforeRender	Mark	863.772
afterHydrate	Mark	922.544

Show Details

JavaScript execution time — 0.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://win.com/_next/static/chunks/05d954cf.b5067be4255f49b388da.js	149.085	146.036	1.638
https://win.com/	115.747	4.969	1.515
https://js.intercomcdn.com/frame-modern.13f9a2c8.js	112.292	101.413	5.425
Unattributable	103.103	3.352	0.221

Show Details

Minimizes main-thread work — 0.6 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	315.238
Other	122.189
Style & Layout	48.554
Rendering	43.082
Script Parsing & Compilation	32.274
Parse HTML & CSS	9.848
Garbage Collection	9.335

Show Details

Keep request counts low and transfer sizes small — 35 requests • 611 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	35	625861
Script	13	320481
Other	8	153701
Font	2	78652
Image	9	62909
Stylesheet	2	6277
Document	1	3841
Media	0	0
Third-party	5	116859

Show Details

Minimize third-party usage — Third-party code blocked the main thread for 20 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	116859	24.271

Show Details

Largest Contentful Paint element — 0 elements found
The element which was identified as the Largest Contentful Paint.

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
Play competitive skill-based games and win real money.	0.000576622012083
Win.com is an innovative gaming platform where you can beat the competition to …	0.00011557656947728
SUBSCRIBE	2.4094869100779E-5

Show Details

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

URL	Start Time (Ms)	Duration (Ms)
https://win.com/_next/static/chunks/05d954cf.b5067be4255f49b388da.js	359	146
https://js.intercomcdn.com/frame-modern.13f9a2c8.js	920	89

Show Details

Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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

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

Diagnostics

Avoid an excessive DOM size — 1,371 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		1371
Maximum DOM Depth	femergenode	14
Maximum Child Elements	Altwinner	17

Show Details

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

URL	Potential Savings (Ms)
https://win.com/fonts/Manrope-ExtraBold.ttf	258.28499998897
https://win.com/fonts/Manrope-Regular.ttf	307.01800016686

Show Details

Some third-party resources can be lazy loaded with a facade — 1 facade alternative available
Consider replacing third-party embeds with a facade until they are required (use lazy loading).

Product	Transfer Size (Bytes)	Main-Thread Blocking Time (Ms)
Intercom Widget (Customer Success)	116859	24.271

Show Details

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

URL	Failing Elements
https://win.com/images/win-logo.svg	Flame
https://win.com/images/social-media/email.svg	Email

Show Details

Accessibility

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

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.

`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.

ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.

ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.

ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

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.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

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.

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 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"]`
Win.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have 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.

Failing Elements
html

Show Details

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.

Best Practices

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

Passing (15)
Failing (3)

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.

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 `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

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
Next.js	9.5.3

Show Details

Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

Insecure URL	Request Resolution
http://win.com/	Allowed

Show Details

Includes front-end JavaScript libraries with known security vulnerabilities — 1 vulnerability detected
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.

Library Version	Vulnerability Count	Highest Severity
SHOW DETAILS	1	Medium

Show Details

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Source	Description
SHOW DETAILS	WebSocket connection to 'wss://nexus-websocket-a.intercom.io/pubsub/5-2-f6GliifSS5iMsURYw7abjQ557ocJiNtb9Rvah4fXg3Xazy16KSXKxzEL3FZSuwB0iiRFDmyQu55875bJMfjQ2BooagZCST1xKT?X-Nexus-New-Client=true&X-Nexus-Version=0.7.0&user_role=undefined' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED

Show Details

SEO

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

Passing (14)
Manual Checks (1)

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

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

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 win.com. This includes details about web app manifests.

Installable

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

PWA Optimized

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.

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 win.com on mobile screens.

Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Does not set 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

Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.

Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.

Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on mobile

Performance

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

Metrics

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

Speed Index — 2.6 s
The time taken for the page contents to be visibly populated.

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