bata.com

bata.com is SSL secured

Free website and domain report on bata.com

Last Updated: 28th May, 2021 Update Now
Overview

Snoop Summary for bata.com

This is a free and comprehensive report about bata.com. Bata.com is hosted in Frankfurt am Main, Hesse in Germany on a server with an IP address of 35.157.152.55, where the local currency is EUR and German is the local language. Our records indicate that bata.com is owned/operated by Bata Brands SA. Bata.com has the potential to be earning an estimated $11 USD per day from advertising revenue. If bata.com was to be sold it would possibly be worth $8,315 USD (based on the daily revenue potential of the website over a 24 month period). Bata.com receives an estimated 3,992 unique visitors every day - a large amount of traffic! This report was last updated 28th May, 2021.

About bata.com

Site Preview: bata.com bata.com
Title: Bata | Quality Shoes and Bags for Women, Men and Kids Since 1894
Description: Topolanek Visits the Bata Shoe Museum ... I am doing a research project on Bata and I would like to receive more corporate information, who can I contact? We do try to make as much information available on www.bata.com as we can. For more country specific information you can search on our local web sites . If the information you are looking for is not available on any of our web sites it means that it is considered proprietary to the nature of our business and can not be made public. ...
Keywords and Tags: beauty, fashion
Related Terms: bata, bata india, bata shoes, bata shoes online india, can yaman, can..., good looking can not stop., information regionale, information.com, skeptical information
Fav Icon:
Age: Over 29 years old
Domain Created: 13th December, 1994
Domain Updated: 10th November, 2020
Domain Expires: 11th December, 2022
Review

Snoop Score

3/5 (Great!)

Valuation

$8,315 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 156,860
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: 3,992
Monthly Visitors: 121,503
Yearly Visitors: 1,457,068
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $11 USD
Monthly Revenue: $346 USD
Yearly Revenue: $4,153 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: bata.com 8
Domain Name: bata 4
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.28 seconds
Load Time Comparison: Faster than 70% of sites

PageSpeed Insights

Avg. (All Categories) 75
Performance 91
Accessibility 87
Best Practices 80
SEO 80
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://bata.com/
Updated: 28th May, 2021

2.86 seconds
First Contentful Paint (FCP)
16%
62%
22%

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

Simulate loading on desktop
91

Performance

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

Metrics

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

Other

First CPU Idle — 0.8 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive bata.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://bata.com/
http/1.1
0
226.05999989901
138
0
301
https://bata.com/
http/1.1
226.73200001009
807.34800000209
3665
10868
200
text/html
Document
https://bata.com/css/bootstrap.min.css?v=4_6_0
http/1.1
828.43999995384
1702.9409999959
161744
161409
200
text/css
Stylesheet
https://bata.com/css/style.css?v=06052021-v12
http/1.1
828.7559999153
1525.525999954
21201
20868
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Montserrat:wght@400;500;600;900&display=swap
h2
829.86499997787
840.22199991159
1395
7032
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-403468-7
h2
832.07299991045
857.70299995784
36643
90740
200
application/javascript
Script
https://com-cdn.bata.eu/images/logo.svg
h2
832.98299997114
963.52099999785
1410
2099
200
image/svg+xml
Image
https://com-cdn.bata.eu/images/be-surprised.svg?v=4
h2
833.19499995559
964.60199996363
2771
6156
200
image/svg+xml
Image
https://com-cdn.bata.eu/images/logo-white.svg
h2
833.41699989978
964.18099990115
1491
2188
200
image/svg+xml
Image
https://bata.com/js/jquery-3.6.0.min.js
http/1.1
830.18399996217
1408.9449999155
89849
89501
200
application/javascript
Script
https://bata.com/js/jquery-ui.min.js
http/1.1
831.0749999946
1811.0859999433
240788
240439
200
application/javascript
Script
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
http/1.1
831.2679999508
1601.9669999368
84726
84378
200
application/javascript
Script
https://bata.com/js/core.js?94E02A0B99
http/1.1
831.64699992631
1412.3249999247
7730
7384
200
application/javascript
Script
https://bata.com/js/jquery.slimscroll.js
http/1.1
831.87699993141
1534.9379999097
14179
13832
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1729.7259999905
1735.0559999468
20199
49153
200
text/javascript
Script
https://bata.com/images/00458_bata_ep06_grafika_web.jpg
http/1.1
1739.164999919
2435.9809999587
319249
318912
200
image/jpeg
Image
https://com-cdn.bata.eu/images/arrow-bottom.svg
h2
1740.0030000135
1752.9459999641
784
513
200
image/svg+xml
Image
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_bZF3gnD_vx3rCs.woff2
h2
1741.9539999682
1746.0769999307
14072
13464
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
h2
1743.2979999576
1748.4359999653
14248
13640
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v15/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
h2
1743.5619999887
1746.579999919
14316
13708
200
font/woff2
Font
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=193564373&t=pageview&_s=1&dl=https%3A%2F%2Fbata.com%2F&ul=en-us&de=UTF-8&dt=Bata%20%7C%20Quality%20Shoes%20and%20Bags%20for%20Women%2C%20Men%20and%20Kids%20Since%201894&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=1908128416&gjid=1952578588&cid=1102722383.1622212896&tid=UA-403468-7&_gid=547495042.1622212896&_r=1&gtm=2ou5q1&z=306185
h2
1829.5919999946
1834.3089999398
612
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j90&tid=UA-403468-7&cid=1102722383.1622212896&jid=1908128416&gjid=1952578588&_gid=547495042.1622212896&_u=YEBAAUAAAAAAAC~&z=495653936
h2
1838.3199999807
1850.3609999316
685
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j90&tid=UA-403468-7&cid=1102722383.1622212896&jid=1908128416&_u=YEBAAUAAAAAAAC~&z=212913355
h2
1891.5809999453
1901.7179999501
678
42
200
image/gif
Image
https://www.bata.eu/get-country/?callback=jQuery3600863907276097654_1622212896304&_=1622212896305
http/1.1
1898.9069999661
2700.5869999994
623
155
200
text/html
Script
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)
857.483
10.575
870.162
5.138
886.421
6.287
912.841
11.918
1750.379
9.252
1759.71
16.658
1776.389
25.864
1802.547
22.08
1841.643
34.053
1889.719
44.52
1938.08
22.685
2494.039
30.467
2747.693
5.392
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Bata.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Bata.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 4 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Bata.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bata.com/css/style.css?v=06052021-v12
21201
3764
Minify JavaScript — Potential savings of 10 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Bata.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bata.com/js/jquery.slimscroll.js
14179
7902
https://bata.com/js/core.js?94E02A0B99
7730
2250
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 138 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://bata.com/images/00458_bata_ep06_grafika_web.jpg
318912
141736
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 580 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://bata.com/
581.612
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Bata.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://bata.com/
190
https://bata.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Bata.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
168
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 1,029 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://bata.com/images/00458_bata_ep06_grafika_web.jpg
319249
https://bata.com/js/jquery-ui.min.js
240788
https://bata.com/css/bootstrap.min.css?v=4_6_0
161744
https://bata.com/js/jquery-3.6.0.min.js
89849
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
84726
https://www.googletagmanager.com/gtag/js?id=UA-403468-7
36643
https://bata.com/css/style.css?v=06052021-v12
21201
https://www.google-analytics.com/analytics.js
20199
https://fonts.gstatic.com/s/montserrat/v15/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
14316
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
14248
Avoids an excessive DOM size — 153 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
153
Maximum DOM Depth
13
Maximum Child Elements
47
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Bata.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.0 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://bata.com/
103.963
17.338
2.097
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
134.504
Other
67.031
Rendering
37.786
Style & Layout
32.36
Parse HTML & CSS
23.662
Script Parsing & Compilation
18.189
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 24 requests • 1,029 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
24
1053196
Script
8
494737
Image
6
326383
Stylesheet
3
184340
Font
3
42636
Document
1
3665
Other
3
1435
Media
0
0
Third-party
14
109927
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)
44031
0
36643
0
20811
0
685
0
678
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
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.0044441292356186
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.

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

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

Opportunities

Eliminate render-blocking resources — Potential savings of 480 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Bata.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://bata.com/css/bootstrap.min.css?v=4_6_0
161744
390
https://bata.com/css/style.css?v=06052021-v12
21201
190
https://fonts.googleapis.com/css2?family=Montserrat:wght@400;500;600;900&display=swap
1395
230
Remove unused CSS — Potential savings of 168 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Bata.com 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://bata.com/css/bootstrap.min.css?v=4_6_0
161744
158329
https://bata.com/css/style.css?v=06052021-v12
21201
14203
Remove unused JavaScript — Potential savings of 318 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://bata.com/js/jquery-ui.min.js
240788
217034
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
84726
70397
https://bata.com/js/jquery-3.6.0.min.js
89849
37825
Enable text compression — Potential savings of 454 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bata.com/js/jquery-ui.min.js
240439
175848
https://bata.com/css/bootstrap.min.css?v=4_6_0
161409
137304
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
84378
62541
https://bata.com/js/jquery-3.6.0.min.js
89501
58554
https://bata.com/css/style.css?v=06052021-v12
20868
15514
https://bata.com/js/jquery.slimscroll.js
13832
10020
https://bata.com/js/core.js?94E02A0B99
7384
5162

Diagnostics

Serve static assets with an efficient cache policy — 14 resources found
Bata.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://bata.com/images/00458_bata_ep06_grafika_web.jpg
0
319249
https://bata.com/js/jquery-ui.min.js
0
240788
https://bata.com/css/bootstrap.min.css?v=4_6_0
0
161744
https://bata.com/js/jquery-3.6.0.min.js
0
89849
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
0
84726
https://bata.com/css/style.css?v=06052021-v12
0
21201
https://bata.com/js/jquery.slimscroll.js
0
14179
https://bata.com/js/core.js?94E02A0B99
0
7730
https://com-cdn.bata.eu/images/be-surprised.svg?v=4
0
2771
https://com-cdn.bata.eu/images/logo-white.svg
0
1491
https://com-cdn.bata.eu/images/logo.svg
0
1410
https://com-cdn.bata.eu/images/arrow-bottom.svg
0
784
https://www.bata.eu/get-country/?callback=jQuery3600863907276097654_1622212896304&_=1622212896305
0
623
https://www.google-analytics.com/analytics.js
7200000
20199
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
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://com-cdn.bata.eu/images/logo.svg
87

Accessibility

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

Contrast

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

Tables and lists

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

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
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.

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

Names and labels

Buttons do not 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.
Failing Elements

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that bata.com 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.

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.6.0
jQuery
3.6.0
jQuery UI
1.11.4
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
https://bata.com/js/bootstrap.bundle.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://bata.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 1 vulnerability detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
1
High
80

SEO

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

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

Links are not 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.

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

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of bata.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.
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) 67
Performance 41
Accessibility 87
Best Practices 80
SEO 83
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://bata.com/
Updated: 28th May, 2021

3.54 seconds
First Contentful Paint (FCP)
22%
44%
34%

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

Simulate loading on mobile
41

Performance

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

Metrics

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

Opportunities

Properly size images
Images can slow down the page's load time. Bata.com should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 3 KiB
Time to Interactive can be slowed down by resources on the page. Bata.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://com-cdn.bata.eu/images/be-surprised.svg?v=4
2771
2771
Minify CSS — Potential savings of 4 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Bata.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bata.com/css/style.css?v=06052021-v12
21201
3764
Minify JavaScript — Potential savings of 10 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Bata.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bata.com/js/jquery.slimscroll.js
14179
7902
https://bata.com/js/core.js?94E02A0B99
7730
2250
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Bata.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://bata.com/
630
https://bata.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Bata.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
168
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://com-cdn.bata.eu/images/logo.svg
0

Diagnostics

Avoids enormous network payloads — Total size was 898 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://bata.com/js/jquery-ui.min.js
240788
https://bata.com/images/00458_bata_ep06_grafika_web-mobile.jpg
199761
https://bata.com/css/bootstrap.min.css?v=4_6_0
161744
https://bata.com/js/jquery-3.6.0.min.js
89849
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
84726
https://www.googletagmanager.com/gtag/js?id=UA-403468-7
36643
https://bata.com/css/style.css?v=06052021-v12
21201
https://www.google-analytics.com/analytics.js
20199
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
14204
https://bata.com/js/jquery.slimscroll.js
14179
Avoids an excessive DOM size — 147 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
147
Maximum DOM Depth
12
Maximum Child Elements
47
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Bata.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 — 23 requests • 898 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
23
919320
Script
8
494738
Image
6
206895
Stylesheet
3
184340
Font
2
28232
Document
1
3665
Other
3
1450
Media
0
0
Third-party
13
95524
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.0048516167534722
0.00012289259168837
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 — 7 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://bata.com/
859
799
https://www.google-analytics.com/analytics.js
4283
400
https://bata.com/js/jquery-3.6.0.min.js
5400
367
https://bata.com/js/jquery-ui.min.js
7770
349
https://bata.com/
3060
293
https://bata.com/css/style.css?v=06052021-v12
4020
237
Unattributable
636
223
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

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

Other

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://bata.com/
http/1.1
0
201.212999993
153
0
301
https://bata.com/
http/1.1
201.85000007041
880.11600007303
3665
10868
200
text/html
Document
https://bata.com/css/bootstrap.min.css?v=4_6_0
http/1.1
896.97400003206
1799.1230000043
161744
161409
200
text/css
Stylesheet
https://bata.com/css/style.css?v=06052021-v12
http/1.1
897.27499999572
1624.0890000481
21201
20868
200
text/css
Stylesheet
https://fonts.googleapis.com/css2?family=Montserrat:wght@400;500;600;900&display=swap
h2
897.54100004211
979.32899999432
1395
7032
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-403468-7
h2
900.76800005045
980.38100008853
36643
90740
200
application/javascript
Script
https://com-cdn.bata.eu/images/logo.svg
h2
900.92699998058
1179.1090000188
1410
2099
200
image/svg+xml
Image
https://com-cdn.bata.eu/images/be-surprised.svg?v=4
h2
901.39999997336
1079.3700000504
2771
6156
200
image/svg+xml
Image
https://com-cdn.bata.eu/images/logo-white.svg
h2
902.60600007605
1079.8080000095
1491
2188
200
image/svg+xml
Image
https://bata.com/js/jquery-3.6.0.min.js
http/1.1
899.58000008482
1779.7770000761
89849
89501
200
application/javascript
Script
https://bata.com/js/jquery-ui.min.js
http/1.1
900.01400001347
1982.3920000345
240788
240439
200
application/javascript
Script
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
http/1.1
900.24400001857
1695.5549999839
84726
84378
200
application/javascript
Script
https://bata.com/js/core.js?94E02A0B99
http/1.1
900.35500004888
1517.5049999962
7730
7384
200
application/javascript
Script
https://bata.com/js/jquery.slimscroll.js
http/1.1
900.59500001371
1422.4399999948
14179
13832
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1881.7290000152
1886.7380000884
20199
49153
200
text/javascript
Script
https://bata.com/images/00458_bata_ep06_grafika_web-mobile.jpg
http/1.1
1889.1580000054
2399.3689999916
199761
199424
200
image/jpeg
Image
https://com-cdn.bata.eu/images/arrow-bottom.svg
h2
1889.70900001
2078.5819999874
784
513
200
image/svg+xml
Image
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_bZF3gnD_vx3rCs.woff2
h2
1890.9270000877
1894.4270000793
14028
13464
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v15/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
h2
1891.1439999938
1893.8850000268
14204
13640
200
font/woff2
Font
https://www.google-analytics.com/j/collect?v=1&_v=j90&a=67642862&t=pageview&_s=1&dl=https%3A%2F%2Fbata.com%2F&ul=en-us&de=UTF-8&dt=Bata%20%7C%20Quality%20Shoes%20and%20Bags%20for%20Women%2C%20Men%20and%20Kids%20Since%201894&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=659113811&gjid=1592500475&cid=2027347490.1622212919&tid=UA-403468-7&_gid=169487843.1622212919&_r=1&gtm=2ou5q1&z=515194692
h2
2102.4560000515
2105.6980000576
612
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j90&tid=UA-403468-7&cid=2027347490.1622212919&jid=659113811&gjid=1592500475&_gid=169487843.1622212919&_u=YEBAAUAAAAAAAC~&z=1066178188
h2
2287.3890000628
2291.4309999906
685
2
200
text/plain
XHR
https://www.bata.eu/get-country/?callback=jQuery36005610471013020586_1622212918541&_=1622212918542
http/1.1
2292.472000001
2996.5030000312
624
156
200
text/html
Script
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j90&tid=UA-403468-7&cid=2027347490.1622212919&jid=659113811&_u=YEBAAUAAAAAAAC~&z=101521615
h2
2297.5340000121
2305.6240000296
678
42
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
979.11
9.733
990.831
5.419
1084.632
9.827
1517.881
55.701
1719.653
59.362
1895.869
8.69
1904.617
73.216
1977.852
17.185
1995.253
91.695
2098.084
100.037
2202.027
174.672
2381.071
8.571
2503.554
199.627
3093.958
7.141
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

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

Other

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

Opportunities

Remove unused CSS — Potential savings of 166 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Bata.com 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://bata.com/css/bootstrap.min.css?v=4_6_0
161744
158329
https://bata.com/css/style.css?v=06052021-v12
21201
11987
Serve images in next-gen formats — Potential savings of 81 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://bata.com/images/00458_bata_ep06_grafika_web-mobile.jpg
199424
83368

Diagnostics

Reduce JavaScript execution time — 1.5 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://bata.com/
1273.504
297.52
7.372
https://bata.com/js/jquery-3.6.0.min.js
428.356
411.532
9.424
https://www.google-analytics.com/analytics.js
418.236
400.412
6.608
https://bata.com/js/jquery-ui.min.js
402.404
79.888
26.38
Unattributable
352.3
4.764
0.672
https://bata.com/js/jquery.slimscroll.js
249.608
0.576
249.032
https://bata.com/css/style.css?v=06052021-v12
237.448
0
0
https://www.googletagmanager.com/gtag/js?id=UA-403468-7
63.224
35.376
10.176
Minimize main-thread work — 3.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1252.052
Rendering
822.536
Other
712.312
Script Parsing & Compilation
321.624
Parse HTML & CSS
308.176
Style & Layout
82.6

Metrics

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

Other

First CPU Idle — 7.2 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 400 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 200 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive bata.com as laggy when the latency is higher than 0.05 seconds.
First Contentful Paint (3G) — 6705 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 2,100 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Bata.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://bata.com/css/bootstrap.min.css?v=4_6_0
161744
1980
https://bata.com/css/style.css?v=06052021-v12
21201
780
https://fonts.googleapis.com/css2?family=Montserrat:wght@400;500;600;900&display=swap
1395
780
Remove unused JavaScript — Potential savings of 323 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://bata.com/js/jquery-ui.min.js
240788
217133
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
84726
70397
https://bata.com/js/jquery-3.6.0.min.js
89849
43114
Enable text compression — Potential savings of 454 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bata.com/js/jquery-ui.min.js
240439
175848
https://bata.com/css/bootstrap.min.css?v=4_6_0
161409
137304
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
84378
62541
https://bata.com/js/jquery-3.6.0.min.js
89501
58554
https://bata.com/css/style.css?v=06052021-v12
20868
15514
https://bata.com/js/jquery.slimscroll.js
13832
10020
https://bata.com/js/core.js?94E02A0B99
7384
5162
Reduce initial server response time — Root document took 680 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://bata.com/
679.263

Diagnostics

Serve static assets with an efficient cache policy — 14 resources found
Bata.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://bata.com/js/jquery-ui.min.js
0
240788
https://bata.com/images/00458_bata_ep06_grafika_web-mobile.jpg
0
199761
https://bata.com/css/bootstrap.min.css?v=4_6_0
0
161744
https://bata.com/js/jquery-3.6.0.min.js
0
89849
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
0
84726
https://bata.com/css/style.css?v=06052021-v12
0
21201
https://bata.com/js/jquery.slimscroll.js
0
14179
https://bata.com/js/core.js?94E02A0B99
0
7730
https://com-cdn.bata.eu/images/be-surprised.svg?v=4
0
2771
https://com-cdn.bata.eu/images/logo-white.svg
0
1491
https://com-cdn.bata.eu/images/logo.svg
0
1410
https://com-cdn.bata.eu/images/arrow-bottom.svg
0
784
https://www.bata.eu/get-country/?callback=jQuery36005610471013020586_1622212918541&_=1622212918542
0
624
https://www.google-analytics.com/analytics.js
7200000
20199
Reduce the impact of third-party code — Third-party code blocked the main thread for 340 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)
20811
338.74
36643
0
29627
0
685
0
678
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 Failing Elements
https://com-cdn.bata.eu/images/logo.svg
87

Accessibility

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

Contrast

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

Tables and lists

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

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
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.

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

Names and labels

Buttons do not 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.
Failing Elements

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that bata.com 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.

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.6.0
jQuery
3.6.0
jQuery UI
1.11.4
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://bata.com/js/bootstrap.bundle.min.js?v=4_6_0
https://bata.com/js/bootstrap.bundle.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://bata.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 1 vulnerability detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
1
High
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for bata.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 bata.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
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.
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.
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

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

Links are not 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.

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

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of bata.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.
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: 35.157.152.55
Continent: Europe
Country: Germany
Germany Flag
Region: Hesse
City: Frankfurt am Main
Longitude: 8.6843
Latitude: 50.1188
Currencies: EUR
Languages: German

Web Hosting Provider

Name IP Address
A100 ROW GmbH
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
MarkMonitor, Inc. 172.64.148.104
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: *.bata.com
Issued By: Starfield Secure Certificate Authority - G2
Valid From: 14th May, 2020
Valid To: 14th May, 2022
Subject: CN = *.bata.com
O = Bata Brands SA
L = Lausanne
S = CH
Hash: c19500ce
Issuer: CN = Starfield Secure Certificate Authority - G2
OU = http://certs.starfieldtech.com/repository/
O = Starfield Technologies, Inc.
S = US
Version: 2
Serial Number: 9283786068071772817
Serial Number (Hex): 80D6A23DC6237291
Valid From: 14th May, 2024
Valid To: 14th May, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:25:45:81:68:50:26:38:3D:3B:2D:2C:BE:CD:6A:D9:B6:3D:B3:66:63
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.starfieldtech.com/sfig2s2-2.crl

Certificate Policies: Policy: 2.16.840.1.114414.1.7.23.2
CPS: http://certificates.starfieldtech.com/repository/
Policy: 2.23.140.1.2.2

Authority Information Access: OCSP - URI:http://ocsp.starfieldtech.com/
CA Issuers - URI:http://certificates.starfieldtech.com/repository/sfig2.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : A4:B9:09:90:B4:18:58:14:87:BB:13:A2:CC:67:70:0A:
3C:35:98:04:F9:1B:DF:B8:E3:77:CD:0E:C8:0D:DC:10
Timestamp : May 14 09:26:44.541 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:08:D4:43:82:19:C5:4E:F8:26:DF:9F:45:
96:FD:47:3B:DB:4A:B9:FC:85:26:8A:0A:5B:D0:40:8F:
B1:C3:78:DA:02:20:7B:1A:FD:3D:BC:AE:7F:29:55:C3:
3D:33:8D:69:9C:45:8F:03:EC:7F:68:CF:AC:9D:76:E5:
78:F4:7E:4F:35:3A
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : BB:D9:DF:BC:1F:8A:71:B5:93:94:23:97:AA:92:7B:47:
38:57:95:0A:AB:52:E8:1A:90:96:64:36:8E:1E:D1:85
Timestamp : May 14 09:26:45.616 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C2:88:F1:A9:0B:25:9A:61:D4:16:D1:
59:C6:D2:34:9C:09:F4:A1:BD:95:2B:05:D0:1A:64:57:
C5:65:D7:CC:1E:02:21:00:FA:3A:C6:F1:50:4F:F3:6D:
2B:75:4C:89:50:D0:66:67:16:44:9E:77:A8:9B:C8:E5:
56:CB:98:42:2C:9F:88:8D
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 56:14:06:9A:2F:D7:C2:EC:D3:F5:E1:BD:44:B2:3E:C7:
46:76:B9:BC:99:11:5C:C0:EF:94:98:55:D6:89:D0:DD
Timestamp : May 14 09:26:46.152 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:41:91:F2:6B:13:66:8C:B5:19:96:3F:3B:
70:0D:FA:E1:8D:5F:CD:7C:6B:1D:98:64:92:85:8E:D1:
E7:98:2A:79:02:21:00:E4:16:72:9F:F0:CA:6F:8B:66:
F9:9A:60:F1:BD:10:7E:FD:08:58:81:57:AF:75:D2:52:
0B:88:D6:41:54:39:C3
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:bata.com
DNS:*.bata.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
bata.com. 52.29.197.251 IN 21599
bata.com. 35.157.152.55 IN 21599

NS Records

Host Nameserver Class TTL
bata.com. ns1-05.azure-dns.com. IN 21599
bata.com. ns2-05.azure-dns.net. IN 21599
bata.com. ns3-05.azure-dns.org. IN 21599
bata.com. ns4-05.azure-dns.info. IN 21599

MX Records

Priority Host Server Class TTL
0 bata.com. mx1.hc1194-1.c3s2.iphmx.com. IN 299
10 bata.com. mx2.hc1194-1.c3s2.iphmx.com. IN 299
20 bata.com. bata-com.mail.protection.outlook.com. IN 299

SOA Records

Domain Name Primary NS Responsible Email TTL
bata.com. ns1-05.azure-dns.com. hostmaster.zerigo.com. 3599

TXT Records

Host Value Class TTL
bata.com. MS=ms61035034 IN 3599
bata.com. google-site-verification=6RKLXK4Is8wvih9m6UduAS4WQ5RTEQCIJrF_8BIm-y4 IN 3599
bata.com. v=spf1 IN 3599
bata.com. kaa4cachm8s0rp8kkjsoej31rc IN 3599
bata.com. cisco-ci-domain-verification=7497da41007e7e547d5ec9e763dd6a0638393d81759437dc78a63454a32fe17e IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx/1.14.2
Date: 28th May, 2021
Content-Type: text/html; charset=UTF-8
Access-Control-Allow-Origin: bata.com
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept

Whois Lookup

Created: 13th December, 1994
Changed: 10th November, 2020
Expires: 11th December, 2022
Registrar: MarkMonitor, Inc.
Status: clientUpdateProhibited
clientTransferProhibited
clientDeleteProhibited
Nameservers: ns1-05.azure-dns.com
ns2-05.azure-dns.net
ns3-05.azure-dns.org
ns4-05.azure-dns.info
Owner Organization: Bata Brands SA
Owner Country: CH
Owner Email: Select Request Email Form at https://domains.markmonitor.com/whois/bata.com
Admin Organization: Bata Brands SA
Admin Country: CH
Admin Email: Select Request Email Form at https://domains.markmonitor.com/whois/bata.com
Tech Organization: Bata Brands SA
Tech Country: CH
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/bata.com
Full Whois: Domain Name: bata.com
Registry Domain ID: 223400_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2020-11-10T02:33:51-0800
Creation Date: 1994-12-13T00:00:00-0800
Registrar Registration Expiration Date: 2022-12-11T00:00:00-0800
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2083895770
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Registrant Organization: Bata Brands SA
Registrant State/Province:
Registrant Country: CH
Registrant Email: Select Request Email Form at https://domains.markmonitor.com/whois/bata.com
Admin Organization: Bata Brands SA
Admin State/Province:
Admin Country: CH
Admin Email: Select Request Email Form at https://domains.markmonitor.com/whois/bata.com
Tech Organization: Bata Brands SA
Tech State/Province:
Tech Country: CH
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/bata.com
Name Server: ns2-05.azure-dns.net
Name Server: ns4-05.azure-dns.info
Name Server: ns3-05.azure-dns.org
Name Server: ns1-05.azure-dns.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-05-28T07:41:30-0700 <<<

For more information on WHOIS status codes, please visit:
https://www.icann.org/resources/pages/epp-status-codes

If you wish to contact this domain’s Registrant, Administrative, or Technical
contact, and such email address is not visible above, you may do so via our web
form, pursuant to ICANN’s Temporary Specification. To verify that you are not a
robot, please enter your email address to receive a link to a page that
facilitates email communication with the relevant contact(s).

Web-based WHOIS:
https://domains.markmonitor.com/whois

If you have a legitimate interest in viewing the non-public WHOIS details, send
your request and the reasons for your request to whoisrequest@markmonitor.com
and specify the domain name in the subject line. We will review that request and
may ask for supporting documentation and explanation.

The data in MarkMonitor’s WHOIS database is provided for information purposes,
and to assist persons in obtaining information about or related to a domain
name’s registration record. While MarkMonitor believes the data to be accurate,
the data is provided "as is" with no guarantee or warranties regarding 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) allow, enable, or otherwise support the transmission by email, telephone,
or facsimile of mass, unsolicited, commercial advertising, or spam; or
(2) enable high volume, automated, or electronic processes that send queries,
data, or email to MarkMonitor (or its systems) or the domain name contacts (or
its systems).

MarkMonitor reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by this policy.

MarkMonitor Domain Management(TM)
Protecting companies and consumers in a digital world.

Visit MarkMonitor at https://www.markmonitor.com
Contact us at +1.8007459229
In Europe, at +44.02032062220

Nameservers

Name IP Address
ns1-05.azure-dns.com 13.107.236.5
ns2-05.azure-dns.net 150.171.21.5
ns3-05.azure-dns.org 204.14.183.5
ns4-05.azure-dns.info 208.84.5.5
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$6,007,563 USD 4/5
$52,982,806 USD 5/5
0/5
0/5
$302,631 USD 3/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
$1,267 USD 1/5

Sites hosted on the same IP address