voe.sx

voe.sx is SSL secured

Free website and domain report on voe.sx

Last Updated: 10th April, 2025
Overview

Snoop Summary for voe.sx

This is a free and comprehensive report about voe.sx. Voe.sx is hosted in Russia on a server with an IP address of 186.2.163.208, where the local currency is RUB and Russian is the local language. Our records indicate that voe.sx is privately registered by REDACTED FOR PRIVACY. Voe.sx is expected to earn an estimated $8,481 USD per day from advertising revenue. The sale of voe.sx would possibly be worth $6,190,902 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Voe.sx receives an estimated 910,836 unique visitors every day - an insane amount of traffic! This report was last updated 10th April, 2025.

About voe.sx

Site Preview: voe.sx voe.sx
Title: VOE | Content Delivery Network (CDN) & Video Cloud
Description: Host, share, and watch private videos with VOE, the video hosting provider. Join now for easy, reliable video hosting and sharing.
Keywords and Tags: business, easy, file upload, free upload, gambling, home, marketing, merchandising, popular, provider, reliable, share, share files, video hosting, voe, watch
Related Terms: akamai cdn, cdn 27, cdn 37, cdn com do, cdn optmd com, cdn syndication twimg com, content delivery network, voe azul, what is cdn gigya com
Fav Icon:
Age: Over 6 years old
Domain Created: 19th June, 2018
Domain Updated: 10th August, 2021
Domain Expires: 19th June, 2026
Review

Snoop Score

4/5 (Excellent!)

Valuation

$6,190,902 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,478
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: 910,836
Monthly Visitors: 27,722,973
Yearly Visitors: 332,455,077
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $8,481 USD
Monthly Revenue: $258,125 USD
Yearly Revenue: $3,095,446 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: voe.sx 6
Domain Name: voe 3
Extension (TLD): sx 2

Page Speed Analysis

Average Load Time: 0.87 seconds
Load Time Comparison: Faster than 78% of sites

PageSpeed Insights

Avg. (All Categories) 80
Performance 97
Accessibility 73
Best Practices 83
SEO 91
PWA 56
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://voe.sx/
Updated: 10th January, 2023

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

0.00 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on desktop
97

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for voe.sx. 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.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
Speed Index — 1.3 s
The time taken for the page contents to be visibly populated.
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).
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.017
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 40 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.
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://voe.sx/
http/1.1
0
270.30399999785
290
0
301
text/html
https://voe.sx/
h2
270.63199999975
758.60699999976
4577
13008
200
text/html
Document
https://fonts.googleapis.com/css2?family=Inter:wght@400;500;700&display=swap
h2
764.74999999846
777.99099999902
1436
6846
200
text/css
Stylesheet
https://voe.sx/assets/379412873852/css/site.min.css?c49fd96c54dd560366ff857af838f3bb
h2
765.02599999731
1336.5309999972
26211
178908
200
text/css
Stylesheet
https://static.ads-twitter.com/uwt.js
h2
765.17899999817
948.61799999853
15890
57596
200
application/javascript
Script
https://imasdk.googleapis.com/js/sdkloader/ima3.js
h2
765.44099999956
786.63699999743
126660
378080
200
text/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js
h2
765.62999999805
783.79399999903
28976
89476
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.1/umd/popper.min.js
h2
765.82399999825
787.44000000006
7705
21233
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.6.0/js/bootstrap.min.js
h2
765.99599999827
782.71200000017
14145
63467
200
application/javascript
Script
https://voe.sx/assets/379412873852/images/logos/voe-logo.svg?v=2
h2
1164.8169999971
1309.2550000001
1410
1845
200
image/svg+xml
Image
https://voe.sx/assets/379412873852/images/background/voe-sx-video-streaming-player-with-people.svg
h2
1310.6389999994
1730.7389999987
8686
29403
200
image/svg+xml
Image
https://www.gstatic.com/youtube/img/promos/growth/63277d5c96b46c6f34c17f15bcbf37decfaac2c9844508e4eeac71cf6ccc35d6_280x280.png
h2
1338.0870000001
1438.1269999976
43173
42447
200
image/png
Image
https://voe.sx/assets/379412873852/images/logos/voe-logo-2.svg?v=2
h2
1388.9909999998
1730.3089999987
697
473
200
image/svg+xml
Image
https://voe.sx/assets/379412873852/js/site.min.js?c49fd96c54dd560366ff857af839f3cc
h2
951.97399999961
1162.6770000003
4625
14081
200
application/javascript
Script
https://fonts.gstatic.com/s/inter/v12/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
h2
1393.2609999974
1399.516999998
38708
37780
200
font/woff2
Font
https://mc.yandex.ru/metrika/tag.js
h2
1425.056
1863.5979999999
74103
215900
200
application/javascript
Script
https://mc.yandex.com/sync_cookie_image_check
http/1.1
1907.7780000007
2060.0300000006
528
0
302
text/plain
https://mc.yandex.com/metrika/advert.gif
h2
1909.4299999997
2050.9639999982
374
43
200
image/gif
Image
https://mc.yandex.ru/sync_cookie_image_start?redirect_domain=mc.yandex.com&token=9879.gnNknvK38oYKYSnXOGD4jj5KnXNgnM-EaZTxtvi7OHUpRPQrTh-O7pgLzlInoZBo.AsGpcYbKwKHthPjL-PtjOgfcqBs%2C
http/1.1
2060.3229999979
2204.7099999982
546
0
302
text/plain
https://mc.yandex.com/sync_cookie_image_decide?token=9879.Zz5jFKjNUh9AaSjeZUDYcEu8MeGLnNEkabPK7gv8gnofevgZzBMqP5sWEUoVfig2Th247ogjNSMDejYAXOK9_UINwKV2uVOWJB_8G5G1B5o%2C.7bgryXLbFcmC5j_WQznGDWwIEFk%2C
h2
2204.9659999975
2351.6449999988
264
75
400
text/html
Image
https://mc.yandex.com/watch/60896098?wmode=7&page-url=https%3A%2F%2Fvoe.sx%2F&charset=utf-8&browser-info=pv%3A1%3Avf%3Awzrng0ylweo7u6lqi2r53%3Afp%3A1423%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A943%3Acn%3A1%3Adp%3A0%3Als%3A1624585375434%3Ahid%3A218738048%3Az%3A-480%3Ai%3A20230110082612%3Aet%3A1673367973%3Ac%3A1%3Arn%3A318353988%3Arqn%3A1%3Au%3A1673367973880802647%3Aw%3A1350x940%3As%3A800x600x24%3Ask%3A1%3Awv%3A2%3Ads%3A0%2C0%2C%2C0%2C271%2C0%2C%2C666%2C0%2C%2C%2C%2C1426%3Aco%3A0%3Antf%3A1%3Ans%3A1673367970620%3Aadb%3A2%3Arqnl%3A1%3Ast%3A1673367973%3At%3AVOE%20%7C%20Content%20Delivery%20Network%20(CDN)%20%26%20Video%20Cloud&t=gdpr(14)clc(0-0-0)rqnt(1)aw(1)ti(2)
http/1.1
2353.9700000001
2500.2019999993
1872
0
302
text/plain
https://mc.yandex.com/watch/60896098/1?wmode=7&page-url=https%3A%2F%2Fvoe.sx%2F&charset=utf-8&browser-info=pv%3A1%3Avf%3Awzrng0ylweo7u6lqi2r53%3Afp%3A1423%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A943%3Acn%3A1%3Adp%3A0%3Als%3A1624585375434%3Ahid%3A218738048%3Az%3A-480%3Ai%3A20230110082612%3Aet%3A1673367973%3Ac%3A1%3Arn%3A318353988%3Arqn%3A1%3Au%3A1673367973880802647%3Aw%3A1350x940%3As%3A800x600x24%3Ask%3A1%3Awv%3A2%3Ads%3A0%2C0%2C%2C0%2C271%2C0%2C%2C666%2C0%2C%2C%2C%2C1426%3Aco%3A0%3Antf%3A1%3Ans%3A1673367970620%3Aadb%3A2%3Arqnl%3A1%3Ast%3A1673367973%3At%3AVOE%20%7C%20Content%20Delivery%20Network%20%28CDN%29%20%26%20Video%20Cloud&t=gdpr%2814%29clc%280-0-0%29rqnt%281%29aw%281%29ti%282%29
h2
2500.5060000003
2650.4480000003
938
447
200
application/json
XHR
https://mc.yandex.com/sync_cookie_image_check_secondary
http/1.1
2652.9569999984
2806.7029999984
525
0
302
text/plain
https://mc.yandex.ru/sync_cookie_image_start_secondary?redirect_domain=mc.yandex.com&token=9879.PaBCjQb8-oqb-XkR7rcbIkG1EkAs9u9Hk21gfO2JufZjK238uWgp9cZWB8B9VOGm.B25F2aEu9EiOUE75GL33YCpIoxg%2C
http/1.1
2806.9859999996
2960.497
558
0
302
text/plain
https://mc.yandex.com/sync_cookie_image_decide_secondary?token=9879.CJxWXTcSOxaiWRN8vTm0z7ntjBKumtzhDn9u8aozj7JLJbljuSTKZFhGJjza6uma796epqopPH-xz36gN-CKJiMlgXCOC0AewEw_sujEt5o%2C.VF6kdXr_ciBJPJy1Qj1dQ4HDfMI%2C
h2
2960.7529999994
3115.5349999972
217
43
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)
762.909
8.298
1348.033
42.177
1390.22
16.476
1413.297
10.874
1878.07
30.602
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images — Potential savings of 39 KiB
Images can slow down the page's load time. Voe.sx should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/youtube/img/promos/growth/63277d5c96b46c6f34c17f15bcbf37decfaac2c9844508e4eeac71cf6ccc35d6_280x280.png
42447
40160
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Voe.sx should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Voe.sx should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Voe.sx should consider minifying JS files.
Reduce unused CSS — Potential savings of 24 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Voe.sx should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://voe.sx/assets/379412873852/css/site.min.css?c49fd96c54dd560366ff857af838f3bb
26211
24846
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 30 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/youtube/img/promos/growth/63277d5c96b46c6f34c17f15bcbf37decfaac2c9844508e4eeac71cf6ccc35d6_280x280.png
42447
30667.85
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 490 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://voe.sx/
488.971
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Voe.sx should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://voe.sx/
190
https://voe.sx/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Voe.sx 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://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.1/umd/popper.min.js
61
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://voe.sx/assets/379412873852/images/background/voe-sx-video-streaming-player-with-people.svg
0
Avoids enormous network payloads — Total size was 394 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://imasdk.googleapis.com/js/sdkloader/ima3.js
126660
https://mc.yandex.ru/metrika/tag.js
74103
https://www.gstatic.com/youtube/img/promos/growth/63277d5c96b46c6f34c17f15bcbf37decfaac2c9844508e4eeac71cf6ccc35d6_280x280.png
43173
https://fonts.gstatic.com/s/inter/v12/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
38708
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js
28976
https://voe.sx/assets/379412873852/css/site.min.css?c49fd96c54dd560366ff857af838f3bb
26211
https://static.ads-twitter.com/uwt.js
15890
https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.6.0/js/bootstrap.min.js
14145
https://voe.sx/assets/379412873852/images/background/voe-sx-video-streaming-player-with-people.svg
8686
https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.1/umd/popper.min.js
7705
Avoids an excessive DOM size — 133 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
133
Maximum DOM Depth
10
Maximum Child Elements
11
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Voe.sx 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
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.
Minimizes main-thread work — 0.2 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
86.259
Other
37.916
Style & Layout
25.973
Script Parsing & Compilation
12.419
Parse HTML & CSS
8.339
Rendering
4.827
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 — 25 requests • 394 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
25
403114
Script
7
272104
Image
7
54821
Font
1
38708
Stylesheet
2
27647
Other
7
5257
Document
1
4577
Media
0
0
Third-party
18
356618
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)
126660
0
75207
0
50826
0
43173
0
40144
0
15890
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
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.
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 voe.sx on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Other

Eliminate render-blocking resources — Potential savings of 540 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Voe.sx should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Inter:wght@400;500;700&display=swap
1436
230
https://voe.sx/assets/379412873852/css/site.min.css?c49fd96c54dd560366ff857af838f3bb
26211
120
https://static.ads-twitter.com/uwt.js
15890
270
https://imasdk.googleapis.com/js/sdkloader/ima3.js
126660
510
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js
28976
310
Reduce unused JavaScript — Potential savings of 134 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://imasdk.googleapis.com/js/sdkloader/ima3.js
126660
91954
https://mc.yandex.ru/metrika/tag.js
74103
45614
Serve static assets with an efficient cache policy — 9 resources found
Voe.sx 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://mc.yandex.com/sync_cookie_image_decide_secondary?token=9879.CJxWXTcSOxaiWRN8vTm0z7ntjBKumtzhDn9u8aozj7JLJbljuSTKZFhGJjza6uma796epqopPH-xz36gN-CKJiMlgXCOC0AewEw_sujEt5o%2C.VF6kdXr_ciBJPJy1Qj1dQ4HDfMI%2C
0
217
https://www.gstatic.com/youtube/img/promos/growth/63277d5c96b46c6f34c17f15bcbf37decfaac2c9844508e4eeac71cf6ccc35d6_280x280.png
3000000
43173
https://mc.yandex.ru/metrika/tag.js
3600000
74103
https://mc.yandex.com/metrika/advert.gif
3600000
374
https://voe.sx/assets/379412873852/css/site.min.css?c49fd96c54dd560366ff857af838f3bb
2592000000
26211
https://voe.sx/assets/379412873852/images/background/voe-sx-video-streaming-player-with-people.svg
2592000000
8686
https://voe.sx/assets/379412873852/js/site.min.js?c49fd96c54dd560366ff857af839f3cc
2592000000
4625
https://voe.sx/assets/379412873852/images/logos/voe-logo.svg?v=2
2592000000
1410
https://voe.sx/assets/379412873852/images/logos/voe-logo-2.svg?v=2
2592000000
697

Other

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
https://www.gstatic.com/youtube/img/promos/growth/63277d5c96b46c6f34c17f15bcbf37decfaac2c9844508e4eeac71cf6ccc35d6_280x280.png
https://voe.sx/assets/379412873852/images/logos/voe-logo.svg?v=2
https://voe.sx/assets/379412873852/images/background/voe-sx-video-streaming-player-with-people.svg
https://voe.sx/assets/379412873852/images/logos/voe-logo-2.svg?v=2
73

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of voe.sx. 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.
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 alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

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

Best practices

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

Audio and video

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

Contrast

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

Navigation

Heading elements are not 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.
Failing Elements

Best practices

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

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.6.0
jQuery
3.5.1
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.
URL Map URL
https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.6.0/js/bootstrap.min.js
https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.6.0/js/bootstrap.min.js.map
https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.1/umd/popper.min.js
https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.1/umd/popper.min.js.map
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://voe.sx/
Allowed

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
Failed to load resource: the server responded with a status of 400 (Bad Request)
91

SEO

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

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of voe.sx. 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

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 voe.sx 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) 77
Performance 67
Accessibility 84
Best Practices 83
SEO 92
PWA 60
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://voe.sx/
Updated: 10th January, 2023

1.33 seconds
First Contentful Paint (FCP)
86%
9%
5%

0.06 seconds
First Input Delay (FID)
77%
22%
1%

Simulate loading on mobile
67

Performance

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

Metrics

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

Other

Properly size images
Images can slow down the page's load time. Voe.sx should consider serving more appropriate-sized images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Voe.sx should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Voe.sx should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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 490 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://voe.sx/
488.122
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Voe.sx should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://voe.sx/
630
https://voe.sx/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Voe.sx 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://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.1/umd/popper.min.js
61
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 394 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://imasdk.googleapis.com/js/sdkloader/ima3.js
126660
https://mc.yandex.ru/metrika/tag.js
74103
https://www.gstatic.com/youtube/img/promos/growth/63277d5c96b46c6f34c17f15bcbf37decfaac2c9844508e4eeac71cf6ccc35d6_280x280.png
43181
https://fonts.gstatic.com/s/inter/v12/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
38707
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js
28994
https://voe.sx/assets/379412873852/css/site.min.css?c49fd96c54dd560366ff857af838f3bb
26211
https://static.ads-twitter.com/uwt.js
15890
https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.6.0/js/bootstrap.min.js
14147
https://voe.sx/assets/379412873852/images/background/voe-sx-video-streaming-player-with-people.svg
8686
https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.1/umd/popper.min.js
7709
Avoids an excessive DOM size — 133 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
133
Maximum DOM Depth
10
Maximum Child Elements
11
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Voe.sx 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.7 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://voe.sx/
516.316
37.992
7.328
https://mc.yandex.ru/metrika/tag.js
362.456
320.828
26.724
https://imasdk.googleapis.com/js/sdkloader/ima3.js
224.84
178.916
45.116
Unattributable
205.168
9.5
0
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js
85.568
71.72
7.544
Minimizes main-thread work — 1.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
695.38
Style & Layout
322.568
Other
281.6
Script Parsing & Compilation
102.868
Parse HTML & CSS
87.42
Rendering
45.988
Garbage Collection
4.176
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 — 25 requests • 394 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
25
403161
Script
7
272128
Image
7
54829
Font
1
38707
Stylesheet
2
27647
Other
7
5273
Document
1
4577
Media
0
0
Third-party
18
356665
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0058771514892578
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 — 4 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://imasdk.googleapis.com/js/sdkloader/ima3.js
4500
369
https://mc.yandex.ru/metrika/tag.js
3840
242
https://voe.sx/
1170
124
https://voe.sx/
1110
60
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 voe.sx on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://voe.sx/
http/1.1
0
278.54400000069
290
0
301
text/html
https://voe.sx/
h2
278.9969999576
766.12300006673
4577
13008
200
text/html
Document
https://fonts.googleapis.com/css2?family=Inter:wght@400;500;700&display=swap
h2
781.47499996703
790.83700000774
1436
6846
200
text/css
Stylesheet
https://voe.sx/assets/379412873852/css/site.min.css?c49fd96c54dd560366ff857af838f3bb
h2
781.80500003509
1338.1440000376
26211
178908
200
text/css
Stylesheet
https://static.ads-twitter.com/uwt.js
h2
782.1029999759
808.94500005525
15890
57596
200
application/javascript
Script
https://imasdk.googleapis.com/js/sdkloader/ima3.js
h2
782.52000000793
796.40200000722
126660
378080
200
text/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js
h2
782.85900002811
798.3719999902
28994
89476
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.1/umd/popper.min.js
h2
783.19300001021
797.1939999843
7709
21233
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.6.0/js/bootstrap.min.js
h2
783.43599999789
797.74199996609
14147
63467
200
application/javascript
Script
https://voe.sx/assets/379412873852/images/logos/voe-logo.svg?v=2
h2
1247.1280000173
1394.5740000345
1410
1845
200
image/svg+xml
Image
https://voe.sx/assets/379412873852/images/background/voe-sx-video-streaming-player-with-people.svg
h2
1340.487999958
1515.1820000028
8686
29403
200
image/svg+xml
Image
https://www.gstatic.com/youtube/img/promos/growth/63277d5c96b46c6f34c17f15bcbf37decfaac2c9844508e4eeac71cf6ccc35d6_280x280.png
h2
1451.31699997
1458.0950000091
43181
42447
200
image/png
Image
https://voe.sx/assets/379412873852/images/logos/voe-logo-2.svg?v=2
h2
1451.5270000556
1601.2490000576
697
473
200
image/svg+xml
Image
https://voe.sx/assets/379412873852/js/site.min.js?c49fd96c54dd560366ff857af839f3cc
h2
835.92900005169
1243.8679999905
4625
14081
200
application/javascript
Script
data
1460.7630000683
1460.9130000463
0
204
200
image/svg+xml
Image
https://fonts.gstatic.com/s/inter/v12/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa1ZL7W0Q5nw.woff2
h2
1464.2590000294
1471.7080000555
38707
37780
200
font/woff2
Font
https://mc.yandex.ru/metrika/tag.js
h2
1564.7779999999
1841.5570000652
74103
215900
200
application/javascript
Script
https://mc.yandex.com/sync_cookie_image_check
http/1.1
1927.732000011
2072.6479999721
544
0
302
text/plain
https://mc.yandex.com/metrika/advert.gif
h2
1931.0190000106
2075.7440000307
374
43
200
image/gif
Image
https://mc.yandex.ru/sync_cookie_image_start?redirect_domain=mc.yandex.com&token=9879.4nCze6pQjylU9YyMYBuvc3uu8u_N3v3ndxFlaYoGTaVureZC4oaTf3X4Ua1u3GMm.wr9GThDDwOfaZFyGsMkXcb3haCQ%2C
http/1.1
2075.4190000007
2215.2599999681
545
0
302
text/plain
https://mc.yandex.com/sync_cookie_image_decide?token=9879.SLbJmO-0WrOFuEuarinxfStDS7FWU8auE78YewVh5_zmV1DSEMyLhXAFUS2lzrku268Ax3NFiP9ZlUpqcrZl38DeZD2J8u6f0K8OOzigeLE%2C.AISb0s6Cd6_1NrpgNuFo63xdVpw%2C
h2
2215.6960000284
2354.3380000629
264
75
400
text/html
Image
https://mc.yandex.com/watch/60896098?wmode=7&page-url=https%3A%2F%2Fvoe.sx%2F&charset=utf-8&browser-info=pv%3A1%3Avf%3Awzrng0ylweo7u6lqi2r53%3Afp%3A1533%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A943%3Acn%3A1%3Adp%3A0%3Als%3A107544314055%3Ahid%3A443882730%3Az%3A-480%3Ai%3A20230110082632%3Aet%3A1673367992%3Ac%3A1%3Arn%3A859597786%3Arqn%3A1%3Au%3A167336799229850578%3Aw%3A360x640%3As%3A360x640x24%3Ask%3A2.625%3Awv%3A2%3Ads%3A0%2C0%2C%2C0%2C280%2C0%2C%2C799%2C1%2C%2C%2C%2C1567%3Aco%3A0%3Antf%3A1%3Ans%3A1673367990307%3Aadb%3A2%3Arqnl%3A1%3Ast%3A1673367993%3At%3AVOE%20%7C%20Content%20Delivery%20Network%20(CDN)%20%26%20Video%20Cloud&t=gdpr(14)clc(0-0-0)rqnt(1)aw(1)ti(2)
http/1.1
2357.7170000644
2512.3319999548
1873
0
302
text/plain
https://mc.yandex.com/watch/60896098/1?wmode=7&page-url=https%3A%2F%2Fvoe.sx%2F&charset=utf-8&browser-info=pv%3A1%3Avf%3Awzrng0ylweo7u6lqi2r53%3Afp%3A1533%3Afu%3A0%3Aen%3Autf-8%3Ala%3Aen-US%3Av%3A943%3Acn%3A1%3Adp%3A0%3Als%3A107544314055%3Ahid%3A443882730%3Az%3A-480%3Ai%3A20230110082632%3Aet%3A1673367992%3Ac%3A1%3Arn%3A859597786%3Arqn%3A1%3Au%3A167336799229850578%3Aw%3A360x640%3As%3A360x640x24%3Ask%3A2.625%3Awv%3A2%3Ads%3A0%2C0%2C%2C0%2C280%2C0%2C%2C799%2C1%2C%2C%2C%2C1567%3Aco%3A0%3Antf%3A1%3Ans%3A1673367990307%3Aadb%3A2%3Arqnl%3A1%3Ast%3A1673367993%3At%3AVOE%20%7C%20Content%20Delivery%20Network%20%28CDN%29%20%26%20Video%20Cloud&t=gdpr%2814%29clc%280-0-0%29rqnt%281%29aw%281%29ti%282%29
h2
2512.8699999768
2653.9689999772
938
447
200
application/json
XHR
https://mc.yandex.com/sync_cookie_image_check_secondary
http/1.1
2659.0309999883
2800.5279999925
541
0
302
text/plain
https://mc.yandex.ru/sync_cookie_image_start_secondary?redirect_domain=mc.yandex.com&token=9879.XlMEJAeS5XmT9siAgsDoRCh12KZh8mx2S1b6_QUVr0s9fOLdw35OIguiomlyYufj.3NmdTfgbO4wddxNlKgX2AtKj6HY%2C
http/1.1
2801.0960000101
2947.1449999837
542
0
302
text/plain
https://mc.yandex.com/sync_cookie_image_decide_secondary?token=9879.v5lej1l8P4jFt-QoBb2eMUX7qU7x5MSqWeAiOEJYz5jKrmKgpLy_L4DIdt6WQVZ-IvlUATD45xupgyspKlPHIYzIZYZmqW1eedvPAc4nSfc%2C.Z9y-O_Hsqzs5FAZvm0cCmy58__Y%2C
h2
2947.5719999755
3090.5659999698
217
43
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)
774.462
15.107
1340.397
11.236
1351.709
9.287
1361.038
92.308
1453.367
61.976
1515.361
5.145
1520.519
7.213
1533.002
20.569
1553.666
10.442
1577.202
5.474
1868.26
60.61
2038.923
7.276
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Time to Interactive — 4.6 s
The time taken for the page to become fully interactive.
Speed Index — 4.4 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 350 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).

Audits

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

Other

Defer offscreen images — Potential savings of 41 KiB
Time to Interactive can be slowed down by resources on the page. Voe.sx should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/youtube/img/promos/growth/63277d5c96b46c6f34c17f15bcbf37decfaac2c9844508e4eeac71cf6ccc35d6_280x280.png
42447
42447
Reduce unused CSS — Potential savings of 24 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Voe.sx should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://voe.sx/assets/379412873852/css/site.min.css?c49fd96c54dd560366ff857af838f3bb
26211
24995
Serve images in next-gen formats — Potential savings of 30 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/youtube/img/promos/growth/63277d5c96b46c6f34c17f15bcbf37decfaac2c9844508e4eeac71cf6ccc35d6_280x280.png
42447
30667.85
Serve static assets with an efficient cache policy — 9 resources found
Voe.sx 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://mc.yandex.com/sync_cookie_image_decide_secondary?token=9879.v5lej1l8P4jFt-QoBb2eMUX7qU7x5MSqWeAiOEJYz5jKrmKgpLy_L4DIdt6WQVZ-IvlUATD45xupgyspKlPHIYzIZYZmqW1eedvPAc4nSfc%2C.Z9y-O_Hsqzs5FAZvm0cCmy58__Y%2C
0
217
https://www.gstatic.com/youtube/img/promos/growth/63277d5c96b46c6f34c17f15bcbf37decfaac2c9844508e4eeac71cf6ccc35d6_280x280.png
3000000
43181
https://mc.yandex.ru/metrika/tag.js
3600000
74103
https://mc.yandex.com/metrika/advert.gif
3600000
374
https://voe.sx/assets/379412873852/css/site.min.css?c49fd96c54dd560366ff857af838f3bb
2592000000
26211
https://voe.sx/assets/379412873852/images/background/voe-sx-video-streaming-player-with-people.svg
2592000000
8686
https://voe.sx/assets/379412873852/js/site.min.js?c49fd96c54dd560366ff857af839f3cc
2592000000
4625
https://voe.sx/assets/379412873852/images/logos/voe-logo.svg?v=2
2592000000
1410
https://voe.sx/assets/379412873852/images/logos/voe-logo-2.svg?v=2
2592000000
697

Metrics

First Contentful Paint — 3.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 4.0 s
The timing of the largest text or image that is painted.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 2,530 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Voe.sx should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css2?family=Inter:wght@400;500;700&display=swap
1436
780
https://voe.sx/assets/379412873852/css/site.min.css?c49fd96c54dd560366ff857af838f3bb
26211
600
https://static.ads-twitter.com/uwt.js
15890
1080
https://imasdk.googleapis.com/js/sdkloader/ima3.js
126660
2280
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js
28994
1380
https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.1/umd/popper.min.js
7709
150
https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.6.0/js/bootstrap.min.js
14147
150
Reduce unused JavaScript — Potential savings of 134 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://imasdk.googleapis.com/js/sdkloader/ima3.js
126660
91954
https://mc.yandex.ru/metrika/tag.js
74103
45635
Reduce the impact of third-party code — Third-party code blocked the main thread for 270 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)
75190
160.852
126660
93.46
50850
14.088
43181
0
40143
0
15890
0
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
https://voe.sx/assets/379412873852/images/logos/voe-logo.svg?v=2
https://voe.sx/assets/379412873852/images/background/voe-sx-video-streaming-player-with-people.svg
https://voe.sx/assets/379412873852/images/logos/voe-logo-2.svg?v=2
First Contentful Paint (3G) — 7419 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
84

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of voe.sx. 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.
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 alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

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

Best practices

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

Audio and video

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

Contrast

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

Navigation

Heading elements are not 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.
Failing Elements

Best practices

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

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.6.0
jQuery
3.5.1
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.
URL Map URL
https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.6.0/js/bootstrap.min.js
https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.6.0/js/bootstrap.min.js.map
https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.1/umd/popper.min.js
https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.16.1/umd/popper.min.js.map
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://voe.sx/
Allowed

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
Failed to load resource: the server responded with a status of 400 (Bad Request)
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for voe.sx. 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 voe.sx on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
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.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of voe.sx. 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

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 voe.sx 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.
Hosting

Server Location

Server IP Address: 186.2.163.208
Continent: Europe
Country: Russia
Russia Flag
Region:
City:
Longitude: 37.6068
Latitude: 55.7386
Currencies: RUB
Languages: Russian

Web Hosting Provider

Name IP Address
Latin American and Caribbean IP address Regional Registry
Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization:
Country: KN
City: REDACTED FOR PRIVACY
State: Charlestown
Post Code: REDACTED FOR PRIVACY
Email:
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
EPAG Domainservices GmbH 35.215.91.252
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 80/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: voe.sx
Issued By: R10
Valid From: 10th April, 2025
Valid To: 9th July, 2025
Subject: CN = voe.sx
Hash: 8f89602c
Issuer: CN = R10
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x06DB4266F99B5FC0E1863E06820094A66CE4
Serial Number (Hex): 06DB4266F99B5FC0E1863E06820094A66CE4
Valid From: 10th April, 2025
Valid To: 9th July, 2025
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://r10.c.lencr.org/101.crl

Certificate Policies: Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://r10.o.lencr.org
CA Issuers - URI:http://r10.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
Timestamp : Apr 10 11:22:42.077 2025 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:8C:0C:CD:83:76:D3:E8:11:38:A4:A1:
67:BF:C7:21:2C:EE:7F:46:05:34:E0:5B:7D:62:82:C9:
08:4E:1D:E4:D8:02:20:0A:EC:76:06:92:45:05:C7:7D:
13:17:26:22:7B:8F:2F:D8:40:40:AF:55:D3:94:27:28:
B4:2D:4A:04:07:61:46
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
Timestamp : Apr 10 11:22:44.119 2025 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:52:79:2B:41:96:B3:C5:A3:B7:35:C8:5C:
44:CE:68:04:AE:92:64:C1:9C:CB:7C:6B:E3:3A:CD:A4:
44:6E:84:14:02:21:00:98:98:93:69:96:3D:04:78:56:
33:F2:68:2E:9E:B5:EE:5B:C2:9F:30:E9:92:D9:3D:D8:
5C:D1:8B:65:9C:91:FA
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.voe.sx
DNS:voe.sx
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/2 200
server: ddos-guard
content-type: text/html; charset=UTF-8
cache-control: no-cache, private
date: 10th April, 2025
set-cookie: *
strict-transport-security: max-age=31536000
content-security-policy: upgrade-insecure-requests;
vary: Accept-Encoding

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: barbara.ns.cloudflare.com
harley.ns.cloudflare.com
Full Whois:

Nameservers

Name IP Address
barbara.ns.cloudflare.com 173.245.58.248
harley.ns.cloudflare.com 108.162.195.128
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$10 USD
0/5
0/5
0/5
0/5

Sites hosted on the same IP address

Love W3 Snoop?

voe.sx Infographic

voe.sx by the numbers infographic