rozetka.com

rozetka.com may not be SSL secured

Free website and domain report on rozetka.com

Last Updated: 22nd July, 2021 Update Now
Overview

Snoop Summary for rozetka.com

This is a free and comprehensive report about rozetka.com. The domain rozetka.com is currently hosted on a server located in Canada with the IP address 104.247.82.52, where CAD is the local currency and the local language is English. Rozetka.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If rozetka.com was to be sold it would possibly be worth $909 USD (based on the daily revenue potential of the website over a 24 month period). Rozetka.com receives an estimated 432 unique visitors every day - a decent amount of traffic! This report was last updated 22nd July, 2021.

About rozetka.com

Site Preview: rozetka.com rozetka.com
Title: rozetka.com
Description:
Keywords and Tags: parked domain
Related Terms: rozetka, rozetka ua
Fav Icon:
Age: Over 19 years old
Domain Created: 30th December, 2004
Domain Updated: 1st December, 2020
Domain Expires: 30th December, 2021
Review

Snoop Score

1/5

Valuation

$909 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,277,411
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: 432
Monthly Visitors: 13,149
Yearly Visitors: 157,680
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $37 USD
Yearly Revenue: $449 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: rozetka.com 11
Domain Name: rozetka 7
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 73
Performance 94
Accessibility 86
Best Practices 87
SEO 80
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://rozetka.com/
Updated: 22nd July, 2021
Simulate loading on desktop
94

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.043
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

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://rozetka.com/
http/1.1
0
256.65499991737
5656
10407
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
274.67299997807
290.4279998038
57920
156375
200
text/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http/1.1
274.84799991362
291.08899994753
827
829
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
http/1.1
275.11099982075
311.18700001389
1054
1417
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Poppins:300
h2
275.33699991181
294.46999984793
1178
1032
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
http/1.1
275.58899996802
297.65199986286
7453
7000
200
application/javascript
Script
http://rozetka.com/track.php?domain=rozetka.com&toggle=browserjs&uid=MTYyNjk0ODY0MS4yMDQ1OjJjNDUxOWU5MzA0NjUwYTYzZWQzMjhmOWIyY2RmMWFiNTI4MjgzZWE2Mjk2M2M4NzFlNmVlNzM2MzAwOGEwYjA6NjBmOTQ0MjEzMWVjOQ%3D%3D
http/1.1
317.3119998537
447.79499992728
608
0
200
text/html
XHR
http://rozetka.com/ls.php
http/1.1
450.73499996215
598.01199985668
861
0
201
text/javascript
XHR
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
http/1.1
461.36299986392
483.83099981584
15986
15544
200
image/png
Image
https://fonts.gstatic.com/s/poppins/v15/pxiByp8kv8JHgFVrLDz8Z1xlFd2JQEk.woff2
h2
461.89699997194
464.90199980326
8603
7848
200
font/woff2
Font
https://www.google.com/afs/ads/i/iframe.html
h2
474.00699998252
480.31199979596
1626
1243
200
text/html
Document
https://www.google.com/dp/ads?adtest=off&channel=000002%2Cbucket066&cpp=0&hl=en&pcsa=false&client=dp-teaminternet09_3ph&r=m&psid=1349223201&type=3&max_radlink_len=40&terms=Rozetka%20UA%2CRozetka%20ua%2CPhones%2CRozetka%2CElectronics%2CComputers%2CA%20Game%20Online%20Games%2CWhere%20to%20Buy%20a%20Cheap%20Iphone%204S&swp=as-drid-2583476792149048&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300494%2C17300496%2C17300756%2C17300758&format=r5%7Cs&num=0&output=afd_ads&domain_name=rozetka.com&v=3&adext=as1%2Csr1&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1626948641484&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=829&frm=0&uio=ff2sa16fa2sl1sr1-sa14st24lt34-&cont=tc&csize=w522h0&inames=master-1&jsv=12441&rurl=http%3A%2F%2Frozetka.com%2F
h2
478.82999991998
555.81299983896
8999
13928
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
568.66799993441
583.13099993393
58391
157241
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Mate%20SC&display=swap
h2
611.29799997434
628.74699989334
1057
392
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Poppins
h2
618.13299986534
635.07699989714
1174
1020
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Mate%20SC&display=swap
h2
636.22699980624
650.23399982601
1057
392
200
text/css
Stylesheet
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2376ff03
h2
656.59199981019
660.3119999636
987
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
656.95099998266
662.9229998216
889
200
200
image/svg+xml
Image
http://rozetka.com/track.php?domain=rozetka.com&caf=1&toggle=answercheck&answer=yes&uid=MTYyNjk0ODY0MS4yMDQ1OjJjNDUxOWU5MzA0NjUwYTYzZWQzMjhmOWIyY2RmMWFiNTI4MjgzZWE2Mjk2M2M4NzFlNmVlNzM2MzAwOGEwYjA6NjBmOTQ0MjEzMWVjOQ%3D%3D
http/1.1
663.4329999797
913.084999891
610
0
200
text/html
XHR
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
h2
922.94399999082
928.3029998187
14047
35645
200
text/javascript
Script
https://fonts.gstatic.com/s/poppins/v15/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
h2
932.59499990381
935.3969998192
8656
7900
200
font/woff2
Font
https://fonts.gstatic.com/s/matesc/v11/-nF8OGQ1-uoVr2wK-iLT9rGnNwE.woff2
h2
934.5650000032
937.94499989599
10104
9348
200
font/woff2
Font
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
h2
1102.4769998621
1102.6169999968
14047
35645
200
text/javascript
Script
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=ug0txrptexxe&aqid=IUT5YOesIY-QmgTY0KSYAw&psid=1349223201&pbt=bs&adbx=414&adby=84&adbh=471&adbw=522&adbn=master-1&eawp=partner-dp-teaminternet09_3ph&errv=12441802300401730745&csadii=23&csadr=479&lle=0&llm=1000&ifv=1&usr=1
h2
2457.7269998845
2477.3049999494
483
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=1jicy6m5z424&psid=1349223201&pbt=bs&adbx=415&adby=572&adbh=20&adbw=521&adbn=slave-1-1&eawp=partner-dp-teaminternet09_3ph&errv=12441802300401730745&csadii=17&csadr=486&lle=0&llm=1000&ifv=1&usr=1
h2
2458.4539998323
2480.8759998996
483
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=icanaspmc7v7&aqid=IUT5YOesIY-QmgTY0KSYAw&psid=1349223201&pbt=bv&adbx=414&adby=84&adbh=471&adbw=522&adbn=master-1&eawp=partner-dp-teaminternet09_3ph&errv=12441802300401730745&csadii=23&csadr=479&lle=0&llm=1000&ifv=1&usr=1
h2
2958.2959997933
2978.0259998515
483
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=4b7gw7xyuaa&psid=1349223201&pbt=bv&adbx=415&adby=572&adbh=20&adbw=521&adbn=slave-1-1&eawp=partner-dp-teaminternet09_3ph&errv=12441802300401730745&csadii=17&csadr=486&lle=0&llm=1000&ifv=1&usr=1
h2
2958.851999836
2977.8169998899
483
0
204
text/html
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)
269.099
7.88
306.342
10.794
318.027
168.139
489.171
6.659
563.739
6.837
598.525
66.196
666.122
252.42
918.554
5.589
935.536
5.345
946.382
11.885
961.909
137.064
1099.181
7.52
1108.867
124.818
1624.605
6.595
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.

Opportunities

Properly size images
Images can slow down the page's load time. Rozetka.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Rozetka.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Rozetka.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Rozetka.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Rozetka.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 60 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
57920
34981
https://www.google.com/adsense/domains/caf.js
58391
26706
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7000
5173
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 260 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)
http://rozetka.com/
257.652
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Rozetka.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Rozetka.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
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.
Preload Largest Contentful Paint image — Potential savings of 110 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
110

Diagnostics

Avoids enormous network payloads — Total size was 218 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
58391
http://www.google.com/adsense/domains/caf.js
57920
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
15986
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
14047
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
14047
https://fonts.gstatic.com/s/matesc/v11/-nF8OGQ1-uoVr2wK-iLT9rGnNwE.woff2
10104
https://www.google.com/dp/ads?adtest=off&channel=000002%2Cbucket066&cpp=0&hl=en&pcsa=false&client=dp-teaminternet09_3ph&r=m&psid=1349223201&type=3&max_radlink_len=40&terms=Rozetka%20UA%2CRozetka%20ua%2CPhones%2CRozetka%2CElectronics%2CComputers%2CA%20Game%20Online%20Games%2CWhere%20to%20Buy%20a%20Cheap%20Iphone%204S&swp=as-drid-2583476792149048&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300494%2C17300496%2C17300756%2C17300758&format=r5%7Cs&num=0&output=afd_ads&domain_name=rozetka.com&v=3&adext=as1%2Csr1&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1626948641484&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=829&frm=0&uio=ff2sa16fa2sl1sr1-sa14st24lt34-&cont=tc&csize=w522h0&inames=master-1&jsv=12441&rurl=http%3A%2F%2Frozetka.com%2F
8999
https://fonts.gstatic.com/s/poppins/v15/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
8656
https://fonts.gstatic.com/s/poppins/v15/pxiByp8kv8JHgFVrLDz8Z1xlFd2JQEk.woff2
8603
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7453
Uses efficient cache policy on static assets — 6 resources found
Rozetka.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)
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
0
15986
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
0
7453
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
0
1054
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
0
827
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%2376ff03
82800000
987
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
889
Avoids an excessive DOM size — 36 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
36
Maximum DOM Depth
8
Maximum Child Elements
15
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Rozetka.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.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://www.google.com/adsense/domains/caf.js
342.448
315.945
7.905
http://www.google.com/adsense/domains/caf.js
278.616
264.837
4.302
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
133.855
133.098
0.575
Minimizes main-thread work — 0.9 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
760.77399999999
Other
55.755
Style & Layout
22.837
Script Parsing & Compilation
21.17
Parse HTML & CSS
12.298
Garbage Collection
10.242
Rendering
6.992
Keep request counts low and transfer sizes small — 27 requests • 218 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
27
223722
Script
5
151858
Font
3
27363
Image
7
19794
Document
3
16281
Stylesheet
6
6347
Other
3
2079
Media
0
0
Third-party
23
215987
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
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.039708999211978
div
0.0034443498817967
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 5 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)
http://www.google.com/adsense/domains/caf.js
597
252
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
924
137
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
1065
125
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
513
84
https://www.google.com/adsense/domains/caf.js
852
66
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

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

Metrics

Total Blocking Time — 160 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 500 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Rozetka.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
827
190
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
1054
190
https://fonts.googleapis.com/css?family=Poppins:300
1178
230
http://www.google.com/adsense/domains/caf.js
57920
310

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://fonts.gstatic.com/s/poppins/v15/pxiByp8kv8JHgFVrLDz8Z1xlFd2JQEk.woff2
3.0049998313189
https://fonts.gstatic.com/s/poppins/v15/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
2.8019999153912
Reduce the impact of third-party code — Third-party code blocked the main thread for 410 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)
156962
329.947
25320
81.628
31829
0
Avoid `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.
Source
86

Accessibility

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

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.
`[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"]`
Rozetka.com 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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
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.
87

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

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.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 9 insecure requests 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://rozetka.com/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
Allowed
http://rozetka.com/track.php?domain=rozetka.com&toggle=browserjs&uid=MTYyNjk0ODY0MS4yMDQ1OjJjNDUxOWU5MzA0NjUwYTYzZWQzMjhmOWIyY2RmMWFiNTI4MjgzZWE2Mjk2M2M4NzFlNmVlNzM2MzAwOGEwYjA6NjBmOTQ0MjEzMWVjOQ%3D%3D
Allowed
http://rozetka.com/ls.php
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
Allowed
http://rozetka.com/track.php?domain=rozetka.com&caf=1&toggle=answercheck&answer=yes&uid=MTYyNjk0ODY0MS4yMDQ1OjJjNDUxOWU5MzA0NjUwYTYzZWQzMjhmOWIyY2RmMWFiNTI4MjgzZWE2Mjk2M2M4NzFlNmVlNzM2MzAwOGEwYjA6NjBmOTQ0MjEzMWVjOQ%3D%3D
Allowed

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
80

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of rozetka.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.
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.
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

Document does not have 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.

Crawling and Indexing

Page is 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.
Blocking Directive Source

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

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

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

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

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.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest 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) 60
Performance 62
Accessibility 53
Best Practices 87
SEO 75
Progressive Web App 25
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://rozetka.com/
Updated: 22nd July, 2021
Simulate loading on mobile
62

Performance

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

Metrics

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

Opportunities

Properly size images
Images can slow down the page's load time. Rozetka.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Rozetka.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Rozetka.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Rozetka.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Rozetka.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7000
5173
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 80 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)
http://rozetka.com/
75.682
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Rozetka.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Rozetka.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
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.
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 182 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://www.google.com/adsense/domains/caf.js
58308
https://www.google.com/adsense/domains/caf.js
58007
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
14047
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
14047
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/img/bg10wide.png
11010
https://www.google.com/dp/ads?adtest=off&channel=000002%2Cbucket074&cpp=0&hl=en&pcsa=false&client=dp-teaminternet09_3ph&r=m&psid=2819104494&type=3&max_radlink_len=40&terms=Rozetka%20UA%2CRozetka%20ua%2CPhones%2CRozetka%2CElectronics%2CComputers%2CA%20Game%20Online%20Games%2CWhere%20to%20Buy%20a%20Cheap%20Iphone%204S&swp=as-drid-2583476792149048&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300494%2C17300496%2C17300756%2C17300758&format=r5%7Cs&num=0&output=afd_ads&domain_name=rozetka.com&v=3&adext=as1%2Csr1&bsl=8&pac=2&u_his=2&u_tz=-420&dt=1626948653588&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=298&frm=0&uio=ff2sa16fa2sl1sr1-ff1fa1sa13st16lt50-ff1fa1&cont=tc&csize=w316h0&inames=master-1&jsv=18040&rurl=http%3A%2F%2Frozetka.com%2F
9134
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7453
http://rozetka.com/
5638
https://www.google.com/afs/ads/i/iframe.html
1625
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/style.css
1164
Uses efficient cache policy on static assets — 5 resources found
Rozetka.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)
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/img/bg10wide.png
0
11010
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
0
7453
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/style.css
0
1164
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
890
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
846
Avoids an excessive DOM size — 33 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
33
Maximum DOM Depth
5
Maximum Child Elements
15
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Rozetka.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 19 requests • 182 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
19
186180
Script
5
151862
Document
3
16397
Image
7
14678
Other
3
2079
Stylesheet
1
1164
Media
0
0
Font
0
0
Third-party
15
178463
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
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.26297210693359
Avoid long main-thread tasks — 5 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
3617
441
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
3177
440
http://www.google.com/adsense/domains/caf.js
2072
229
http://www.google.com/adsense/domains/caf.js
1867
205
https://www.google.com/adsense/domains/caf.js
2947
192
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

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

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://rozetka.com/
http/1.1
0
74.683999991976
5638
10391
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
87.336999946274
100.27799999807
58308
157241
200
text/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/style.css
http/1.1
87.69499999471
103.77000004519
1164
1728
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
http/1.1
88.058999972418
102.37900004722
7453
7000
200
application/javascript
Script
http://rozetka.com/track.php?domain=rozetka.com&toggle=browserjs&uid=MTYyNjk0ODY1My40Mzk1Ojg5MDE5OTE5ZmNhOWQwMzQwNGNkNzY3M2UwMjFiYmUyZGFkZWFlMjcyNzYyYWU5YWVmMzlkNzkzYTQzZjFmNmQ6NjBmOTQ0MmQ2YjRlYQ%3D%3D
http/1.1
125.49999996554
182.10700002965
608
0
200
text/html
XHR
http://rozetka.com/ls.php
http/1.1
184.52100001741
239.27999997977
861
0
201
text/javascript
XHR
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/img/bg10wide.png
http/1.1
193.82799998857
219.37099995557
11010
10569
200
image/png
Image
https://www.google.com/afs/ads/i/iframe.html
h2
204.88299999852
210.16899996903
1625
1243
200
text/html
Document
https://www.google.com/dp/ads?adtest=off&channel=000002%2Cbucket074&cpp=0&hl=en&pcsa=false&client=dp-teaminternet09_3ph&r=m&psid=2819104494&type=3&max_radlink_len=40&terms=Rozetka%20UA%2CRozetka%20ua%2CPhones%2CRozetka%2CElectronics%2CComputers%2CA%20Game%20Online%20Games%2CWhere%20to%20Buy%20a%20Cheap%20Iphone%204S&swp=as-drid-2583476792149048&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300494%2C17300496%2C17300756%2C17300758&format=r5%7Cs&num=0&output=afd_ads&domain_name=rozetka.com&v=3&adext=as1%2Csr1&bsl=8&pac=2&u_his=2&u_tz=-420&dt=1626948653588&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=298&frm=0&uio=ff2sa16fa2sl1sr1-ff1fa1sa13st16lt50-ff1fa1&cont=tc&csize=w316h0&inames=master-1&jsv=18040&rurl=http%3A%2F%2Frozetka.com%2F
h2
210.92900005169
407.48399996664
9134
14153
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
418.61299995799
432.0819999557
58007
156384
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
488.19900001399
490.95700006001
846
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
488.31899999641
494.11600001622
890
200
200
image/svg+xml
Image
http://rozetka.com/track.php?domain=rozetka.com&caf=1&toggle=answercheck&answer=yes&uid=MTYyNjk0ODY1My40Mzk1Ojg5MDE5OTE5ZmNhOWQwMzQwNGNkNzY3M2UwMjFiYmUyZGFkZWFlMjcyNzYyYWU5YWVmMzlkNzkzYTQzZjFmNmQ6NjBmOTQ0MmQ2YjRlYQ%3D%3D
http/1.1
492.47900000773
547.84200002905
610
0
200
text/html
XHR
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
h2
555.39700004738
559.47400000878
14047
35645
200
text/javascript
Script
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
h2
701.25299994834
701.38600002974
14047
35645
200
text/javascript
Script
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=4849fv1pe5cj&aqid=LUT5YL-DLonymQS6u4PABQ&psid=2819104494&pbt=bs&adbx=10&adby=66.46875&adbh=381&adbw=340&adbah=64%2C64%2C64%2C64%2C88&adbn=master-1&eawp=partner-dp-teaminternet09_3ph&errv=18040280528035421317&csadii=20&csadr=375&lle=0&llm=1000&ifv=1&usr=1
h2
2084.6590000438
2109.3760000076
483
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=5u48644olw8x&psid=2819104494&pbt=bs&adbx=10&adby=472.46875&adbh=18&adbw=340&adbn=slave-1-1&eawp=partner-dp-teaminternet09_3ph&errv=18040280528035421317&csadii=14&csadr=382&lle=0&llm=1000&ifv=1&usr=1
h2
2085.6200000271
2105.8660000563
483
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=dcf0njz52aeh&aqid=LUT5YL-DLonymQS6u4PABQ&psid=2819104494&pbt=bv&adbx=10&adby=66.46875&adbh=381&adbw=340&adbah=64%2C64%2C64%2C64%2C88&adbn=master-1&eawp=partner-dp-teaminternet09_3ph&errv=18040280528035421317&csadii=20&csadr=375&lle=0&llm=1000&ifv=1&usr=1
h2
2584.8840000108
2605.5840000045
483
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=r5hjcq7go49m&psid=2819104494&pbt=bv&adbx=10&adby=472.46875&adbh=18&adbw=340&adbn=slave-1-1&eawp=partner-dp-teaminternet09_3ph&errv=18040280528035421317&csadii=14&csadr=382&lle=0&llm=1000&ifv=1&usr=1
h2
2586.0370000592
2604.8410000512
483
0
204
text/html
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)
85.896
6.788
118.817
102.604
222.773
6.245
417.75
5.986
449.919
47.99
498.555
57.353
555.919
5.74
575.461
12.001
590.5
7.244
597.818
109.931
710.028
110.288
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

First Contentful Paint — 2.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 3.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 3.9 s
The time taken for the page to become fully interactive.

Other

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

Opportunities

Reduce unused JavaScript — Potential savings of 61 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
58308
35345
https://www.google.com/adsense/domains/caf.js
58007
26936

Diagnostics

Reduce JavaScript execution time — 1.8 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js
1108.388
1010.78
28.208
http://www.google.com/adsense/domains/caf.js
332.868
279.124
17.62
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
238.696
236.536
2.16
http://rozetka.com/
162.604
104.216
9.68
Unattributable
97.696
8.952
0.544
https://www.google.com/js/bg/9ed6_nQfnMrUg05r027NxL2aUp_091DFxQGup7yyecw.js
64.672
44.992
8.62
Minimize main-thread work — 2.1 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
1702.764
Other
183.928
Script Parsing & Compilation
78.364
Style & Layout
68.776
Parse HTML & CSS
36.996
Rendering
24.344
Garbage Collection
15.036

Metrics

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

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 1,570 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Rozetka.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/style.css
1164
630
http://www.google.com/adsense/domains/caf.js
58308
930

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 1,080 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)
157100
896.056
19627
180.856
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Avoid `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.
Source
53

Accessibility

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

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.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Rozetka.com 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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

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

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

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.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 8 insecure requests 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://rozetka.com/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/style.css
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
Allowed
http://rozetka.com/track.php?domain=rozetka.com&toggle=browserjs&uid=MTYyNjk0ODY1My40Mzk1Ojg5MDE5OTE5ZmNhOWQwMzQwNGNkNzY3M2UwMjFiYmUyZGFkZWFlMjcyNzYyYWU5YWVmMzlkNzkzYTQzZjFmNmQ6NjBmOTQ0MmQ2YjRlYQ%3D%3D
Allowed
http://rozetka.com/ls.php
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_d339b490/img/bg10wide.png
Allowed
http://rozetka.com/track.php?domain=rozetka.com&caf=1&toggle=answercheck&answer=yes&uid=MTYyNjk0ODY1My40Mzk1Ojg5MDE5OTE5ZmNhOWQwMzQwNGNkNzY3M2UwMjFiYmUyZGFkZWFlMjcyNzYyYWU5YWVmMzlkNzkzYTQzZjFmNmQ6NjBmOTQ0MmQ2YjRlYQ%3D%3D
Allowed

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
75

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of rozetka.com on mobile screens.
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.
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.
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

Document does not have 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.

Crawling and Indexing

Page is 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.
Blocking Directive Source

Mobile Friendly

Document doesn't use legible font sizes — 9.81% 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
#sub
90.19%
10px
9.81%
≥ 12px

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

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

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

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

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.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Server Location

Server IP Address: 104.247.82.52
Continent: North America
Country: Canada
Canada Flag
Region:
City:
Longitude: -79.3716
Latitude: 43.6319
Currencies: CAD
Languages: English
French

Web Hosting Provider

Name IP Address
NEXT DIMENSION INC
Registration

Domain Registrant

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

Domain Registrar

Security

Visitor Safety

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

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
rozetka.com. 104.247.82.52 IN 599

NS Records

Host Nameserver Class TTL
rozetka.com. ns2.fastpark.net. IN 3599
rozetka.com. ns1.fastpark.net. IN 3599

MX Records

Priority Host Server Class TTL
5 rozetka.com. mail.h-email.net. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
rozetka.com. ns1.fastpark.net. hostmaster.rozetka.com. 10799

TXT Records

Host Value Class TTL
rozetka.com. v=spf1 IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 22nd July, 2021
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Accept-CH: ua-mobile
Accept-CH-Lifetime: 30
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALquDFETXRn0Hr05fUP7EJT77xYnPmRbpMy4vk8KYiHnkNpednjOANJcaXDXcKQJN0nXKZJL7TciJD8AoHXK158CAwEAAQ==_YTOlWZ/UMPgrbhsfL6zL+VjOAfzI+J47CVgBOuW9Qf77vXST7fmmMewOxieQJ05P5aDlyvftlt3NTp33CkwZjA==

Whois Lookup

Created: 30th December, 2004
Changed: 1st December, 2020
Expires: 30th December, 2021
Registrar: ENOM, INC.
Status: clientTransferProhibited
Nameservers: ns1.fastpark.net
ns2.fastpark.net
Owner Name: REDACTED FOR PRIVACY
Owner Organization: REDACTED FOR PRIVACY
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner Country: CY
Owner Phone: REDACTED FOR PRIVACY
Owner Email: https://tieredaccess.com/contact/41e3f02b-9416-49de-a2cf-78e2faaa1728
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Full Whois:

Domain Name: rozetka.com
Registry Domain ID: 138513490_DOMAIN_COM-VRSN
Registrar WHOIS Server: WHOIS.ENOM.COM
Registrar URL: WWW.ENOM.COM
Updated Date: 2020-12-01T08:36:31.00Z
Creation Date: 2004-12-30T19:03:10.00Z
Registrar Registration Expiration Date: 2021-12-30T19:03:00.00Z
Registrar: ENOM, INC.
Registrar IANA ID: 48
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street:
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province:
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: CY
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext:
Registrant Fax: REDACTED FOR PRIVACY
Registrant Email: https://tieredaccess.com/contact/41e3f02b-9416-49de-a2cf-78e2faaa1728
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street:
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext:
Admin Fax: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street:
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext:
Tech Fax: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Name Server: NS1.FASTPARK.NET
Name Server: NS2.FASTPARK.NET
DNSSEC: unsigned
Registrar Abuse Contact Email: ABUSE@ENOM.COM
Registrar Abuse Contact Phone: +1.4259744689
URL of the ICANN WHOIS Data Problem Reporting System: HTTP://WDPRS.INTERNIC.NET/
>>> Last update of WHOIS database: 2021-07-22T10:10:38.00Z <<<

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


The data in this whois database is provided to you for information
purposes only, that is, to assist you in obtaining information about or
related to a domain name registration record. We make this information
available "as is," and do not guarantee its accuracy. By submitting a
whois query, you agree that you will use this data only for lawful
purposes and that, under no circumstances will you use this data to: (1)
enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or (2) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic
mail, or by telephone. The compilation, repackaging, dissemination or
other use of this data is expressly prohibited without prior written
consent from us.

We reserve the right to modify these terms at any time. By submitting
this query, you agree to abide by these terms.
Version 6.3 4/3/2002

Nameservers

Name IP Address
ns1.fastpark.net 75.2.14.138
ns2.fastpark.net 99.83.157.32
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$12,117,851 USD 4/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$12,117,851 USD 4/5
$667 USD 1/5
0/5

Sites hosted on the same IP address