Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

zalando.com

zalando.com is SSL secured

Free website and domain report on zalando.com

Last Updated: 4th May, 2023 Update Now
Overview

Snoop Summary for zalando.com

This is a free and comprehensive report about zalando.com. The domain zalando.com is currently hosted on a server located in Mountain View, California in United States with the IP address 130.211.9.113, where USD is the local currency and the local language is English. Zalando.com is expected to earn an estimated $133 USD per day from advertising revenue. The sale of zalando.com would possibly be worth $97,077 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Zalando.com receives an estimated 31,443 unique visitors every day - a massive amount of traffic! This report was last updated 4th May, 2023.

About zalando.com

Site Preview: zalando.com zalando.com
Title: Zalando - Shoes and Fashion Online
Description: Zalando | Buy shoes online: Shoes from top brands.
Keywords and Tags: beauty, fashion, online shopping, popular
Related Terms: adidas gazelle homme zalando, germany zalando, stivali zalando, zalando abiti lunghi, zalando france, zalando germany, zalando it, zalando italia, zalando scarpe donne saldi
Fav Icon:
Age: Over 15 years old
Domain Created: 22nd May, 2008
Domain Updated: 15th June, 2020
Domain Expires: 22nd May, 2021
Review

Snoop Score

4/5 (Excellent!)

Valuation

$97,077 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 24,567
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: 31,443
Monthly Visitors: 957,026
Yearly Visitors: 11,476,695
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $133 USD
Monthly Revenue: $4,047 USD
Yearly Revenue: $48,534 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: zalando.com 11
Domain Name: zalando 7
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.90 seconds
Load Time Comparison: Faster than 47% of sites

PageSpeed Insights

Avg. (All Categories) 82
Performance 99
Accessibility 95
Best Practices 87
SEO 91
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://zalando.com/
Updated: 1st April, 2021

0.59 seconds
First Contentful Paint (FCP)
89%
9%
2%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
99

Performance

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

Metrics

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

Other

First CPU Idle — 0.6 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.6 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive zalando.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://zalando.com/
http/1.1
0
109.55600003945
233
0
301
text/html
https://zalando.com/
h2
110.19600002328
291.95899999468
3391
16397
200
text/html
Document
https://skin.ztat.net/s/tir/zalando/img/MAIN/logos/shops/schuhe.jpg
http/1.1
307.68399999943
493.13200003235
6745
6356
200
image/jpeg
Image
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
h2
307.97300004633
430.05600001197
64670
64204
200
image/jpeg
Image
https://skin2.ztat.net/s/tir/zalando/img/MAIN/sprites/spriteIcon.png
http/1.1
310.40700001176
492.51500004902
89942
89734
200
image/png
Image
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo400.woff
h2
407.39500004565
692.58999999147
14234
13776
200
application/font-woff
Font
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo700.woff
h2
407.64900000067
513.05100001628
14275
13816
200
application/font-woff
Font
https://ip-api.com/json/?fields=country,countryCode
http/1.1
499.16599999415
693.14400001895
184
2
403
application/json
XHR
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)
483.916
9.59
497.708
187.715
886.127
12.717
1902.64
78.244
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Zalando.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Zalando.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Zalando.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Zalando.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Zalando.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Zalando.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images — Potential savings of 15 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
64204
15183
Serve images in next-gen formats — Potential savings of 97 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://skin2.ztat.net/s/tir/zalando/img/MAIN/sprites/spriteIcon.png
89734
63596
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
64204
35910
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 180 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://zalando.com/
182.761
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Zalando.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://zalando.com/
190
https://zalando.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Zalando.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.
URL Potential Savings (Ms)
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
0

Diagnostics

Avoids enormous network payloads — Total size was 189 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://skin2.ztat.net/s/tir/zalando/img/MAIN/sprites/spriteIcon.png
89942
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
64670
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo700.woff
14275
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo400.woff
14234
https://skin.ztat.net/s/tir/zalando/img/MAIN/logos/shops/schuhe.jpg
6745
https://zalando.com/
3391
http://zalando.com/
233
https://ip-api.com/json/?fields=country,countryCode
184
Avoids an excessive DOM size — 44 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
44
Maximum DOM Depth
ZALANDO.DE
5
Maximum Child Elements
ZALANDO.DE ZALANDO.FR ZALANDO.LU ZALANDO.AT ZALANDO.IT ZALANDO.NO ZALANDO.CH ZA…
17
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Zalando.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.2 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://zalando.com/
226.308
95.272
1.698
Unattributable
89.217
78.545
0.205
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
173.817
Style & Layout
109.805
Other
21.003
Rendering
5.306
Parse HTML & CSS
3.691
Script Parsing & Compilation
1.903
Keep request counts low and transfer sizes small — 8 requests • 189 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
8
193674
Image
3
161357
Font
2
28509
Document
1
3391
Other
2
417
Stylesheet
0
0
Media
0
0
Script
0
0
Third-party
6
190050
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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
Zalando - Shoes & Fashion online
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://zalando.com/
342
94
Unattributable
190
78
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.

Diagnostics

Serve static assets with an efficient cache policy — 5 resources found
Zalando.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://skin2.ztat.net/s/tir/zalando/img/MAIN/sprites/spriteIcon.png
0
89942
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
0
64670
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo700.woff
0
14275
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo400.woff
0
14234
https://skin.ztat.net/s/tir/zalando/img/MAIN/logos/shops/schuhe.jpg
0
6745
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://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo400.woff
285.19499994582
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo700.woff
105.4020000156
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of zalando.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

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"]`
Zalando.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
SHOES & FASHION ONLINE - ZALANDO IS AVAILABLE IN THE FOLLOWING COUNTRIES

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 zalando.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

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

Audits

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

Audits

Avoids `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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
SHOW DETAILS
Failed to load resource: the server responded with a status of 403 (Forbidden)
91

SEO

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

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

robots.txt is not valid — 393 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!doctype html>
Syntax not understood
2
<html lang="en">
Syntax not understood
3
<head profile="http://gmpg.org/xfn/11">
Unknown directive
4
<meta charset="UTF-8">
Syntax not understood
5
<title>Zalando - Shoes and Fashion Online</title>
Syntax not understood
7
<meta name="description" content="Zalando | Buy shoes online: Shoes from top brands.">
Unknown directive
8
<meta name="viewport" content="width=device-width, initial-scale=1">
Syntax not understood
9
<meta name="google-site-verification" content="1VHp1WET1lNXsSv7mKcEhpcru_SHBd_VRYBP5cUBWUY">
Syntax not understood
10
<style>
Syntax not understood
15
@font-face {
Syntax not understood
16
font-family: Arimo;
Unknown directive
17
font-style: normal;
Unknown directive
18
font-weight: 400;
Unknown directive
19
src: url('https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo400.woff');
Unknown directive
20
}
Syntax not understood
22
@font-face {
Syntax not understood
23
font-family: 'Arimo';
Unknown directive
24
font-style: normal;
Unknown directive
25
font-weight: 700;
Unknown directive
26
src: url('https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo700.woff');
Unknown directive
27
}
Syntax not understood
29
.wrapper {
Syntax not understood
30
font-family: Arimo, Arial, Helvetica, "DejaVu Sans", "Arial Unicode MS", "Lucida Sans Unicode",
Unknown directive
31
sans-serif;
Syntax not understood
32
margin: 0 auto;
Unknown directive
33
width: 1010px;
Unknown directive
34
}
Syntax not understood
36
.header_headline {
Syntax not understood
37
background: #999999;
Unknown directive
38
color: #ffffff;
Unknown directive
39
font-size: 18px;
Unknown directive
40
font-weight: 500;
Unknown directive
41
letter-spacing: 2px;
Unknown directive
42
line-height: 44px;
Unknown directive
43
margin: 11px 0 0 0;
Unknown directive
44
padding: 0;
Unknown directive
45
text-transform: uppercase;
Unknown directive
46
text-align: center;
Unknown directive
48
}
Syntax not understood
50
.content {
Syntax not understood
51
margin-top: 1px;
Unknown directive
52
overflow: hidden;
Unknown directive
53
}
Syntax not understood
55
.content_image {
Syntax not understood
56
float: left;
Unknown directive
57
height: 399px;
Unknown directive
58
width: 457px;
Unknown directive
59
}
Syntax not understood
61
.nav {
Syntax not understood
62
float: left;
Unknown directive
63
list-style-type: none;
Unknown directive
64
overflow: hidden;
Unknown directive
65
margin: 0;
Unknown directive
66
padding: 0;
Unknown directive
67
width: 553px;
Unknown directive
68
}
Syntax not understood
70
.nav_item {
Syntax not understood
71
display: table;
Unknown directive
72
float: left;
Unknown directive
73
height: 79px;
Unknown directive
74
margin: 0 0 1px 1px;
Unknown directive
75
position: relative;
Unknown directive
76
width: 183px;
Unknown directive
77
}
Syntax not understood
79
.nav_link, .nav_link2 {
Syntax not understood
80
background-color: #f3f3f3;
Unknown directive
81
color: #404040;
Unknown directive
82
display: table-cell;
Unknown directive
83
font-size: 10px;
Unknown directive
84
font-weight: bold;
Unknown directive
85
letter-spacing: .2em;
Unknown directive
86
text-align: center;
Unknown directive
87
text-decoration: none;
Unknown directive
88
text-transform: uppercase;
Unknown directive
89
vertical-align: middle;
Unknown directive
90
width: 100%;
Unknown directive
91
}
Syntax not understood
93
.nav_link:hover, .nav_link2:hover{
Unknown directive
94
background-color: #ddd;
Unknown directive
95
}
Syntax not understood
97
.nav_link:before {
Unknown directive
98
background-image: url("//skin2.ztat.net/s/tir/zalando/img/MAIN/sprites/spriteIcon.png");
Unknown directive
99
background-repeat: no-repeat;
Unknown directive
100
content: '';
Unknown directive
101
display: inline-block;
Unknown directive
102
height: 15px;
Unknown directive
103
margin: 0 20px 0 0;
Unknown directive
104
vertical-align: -4px;
Unknown directive
105
width: 24px;
Unknown directive
106
}
Syntax not understood
108
.nav_link-cz:before {
Unknown directive
109
background-image: url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' version='1.0' width='24' height='18'><rect width='24' height='18' fill='#d7141a'/><rect width='24' height='9' fill='#fff'/><path d='M 12,9 0,0 V 18 z' fill='#11457e'/></svg>");
Unknown directive
111
background-repeat: no-repeat;
Unknown directive
112
content: '';
Unknown directive
113
display: inline-block;
Unknown directive
114
height: 15px;
Unknown directive
115
margin: 0 20px 0 0;
Unknown directive
116
vertical-align: -4px;
Unknown directive
117
width: 24px;
Unknown directive
118
}
Syntax not understood
120
.nav_link-ie:before {
Unknown directive
121
background-image: url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' width='24' height='18'><rect fill='#169b62' width='8' height='18' x='0'/><rect fill='#fff' width='8' height='18' x='8'/><rect fill='#ff883e' x='16' width='8' height='18'/></svg>");
Unknown directive
123
background-repeat: no-repeat;
Unknown directive
124
content: '';
Unknown directive
125
display: inline-block;
Unknown directive
126
height: 15px;
Unknown directive
127
margin: 0 20px 0 0;
Unknown directive
128
vertical-align: -4px;
Unknown directive
129
width: 24px;
Unknown directive
130
}
Syntax not understood
132
.nav_link-de:before {
Unknown directive
133
background-position: 0 0;
Unknown directive
134
}
Syntax not understood
136
.nav_link-nl:before {
Unknown directive
137
background-position: -28px 0;
Unknown directive
138
}
Syntax not understood
140
.nav_link-ch:before {
Unknown directive
141
background-position: -190px 0;
Unknown directive
142
}
Syntax not understood
144
.nav_link-fr:before {
Unknown directive
145
background-position: -55px 0;
Unknown directive
146
}
Syntax not understood
148
.nav_link-be:before {
Unknown directive
149
background-position: -82px 0;
Unknown directive
150
}
Syntax not understood
152
.nav_link-lu:before {
Unknown directive
153
background-position: -268px 0;
Unknown directive
154
}
Syntax not understood
156
.nav_link-at:before {
Unknown directive
157
background-position: -109px 0;
Unknown directive
158
}
Syntax not understood
160
.nav_link-it:before {
Unknown directive
161
background-position: -136px 0;
Unknown directive
162
}
Syntax not understood
164
.nav_link-gb:before {
Unknown directive
165
background-position: -163px 0;
Unknown directive
166
}
Syntax not understood
168
.nav_link-es:before {
Unknown directive
169
background-position: -294px 0;
Unknown directive
170
}
Syntax not understood
172
.nav_link-fi:before {
Unknown directive
173
background-position: -216px 0;
Unknown directive
174
}
Syntax not understood
176
.nav_link-no:before {
Unknown directive
177
background-position: -372px 0;
Unknown directive
178
}
Syntax not understood
180
.nav_link-se:before {
Unknown directive
181
background-position: -320px 0;
Unknown directive
182
}
Syntax not understood
184
.nav_link-pl:before {
Unknown directive
185
background-position: -346px 0;
Unknown directive
186
}
Syntax not understood
188
.nav_link-dk:before {
Unknown directive
189
background-position: -242px 0;
Unknown directive
190
}
Syntax not understood
192
.footer {
Syntax not understood
193
text-align: right;
Unknown directive
194
margin-top: 4px;
Unknown directive
195
}
Syntax not understood
197
.footer_link {
Syntax not understood
198
color: #000;
Unknown directive
199
font-size: 12px;
Unknown directive
200
text-decoration: none;
Unknown directive
201
}
Syntax not understood
203
*+html .nav_link {
Syntax not understood
204
display: block;
Unknown directive
205
height: 48px;
Unknown directive
206
padding-top: 31px;
Unknown directive
207
}
Syntax not understood
209
@media only screen and (min-width:320px) and (max-width:640px){
Unknown directive
210
.wrapper {
Syntax not understood
211
width: 100%;
Unknown directive
212
}
Syntax not understood
214
.content_image {
Syntax not understood
215
display: none;
Unknown directive
216
}
Syntax not understood
218
h1.header_headline span{
Syntax not understood
219
display: none;
Unknown directive
220
}
Syntax not understood
222
h1.header_headline:before {
Unknown directive
223
content: 'Zalando is available in:';
Unknown directive
224
}
Syntax not understood
226
UL.nav {
Syntax not understood
227
width: 100%;
Unknown directive
228
}
Syntax not understood
230
.nav_item {
Syntax not understood
231
-webkit-box-flex: 1;
Unknown directive
232
-webkit-flex-grow: 1;
Unknown directive
233
-ms-flex-positive: 1;
Unknown directive
234
flex-grow: 1;
Unknown directive
235
-webkit-box-sizing: border-box; /* Safari 3.0 - 5.0, Chrome 1 - 9, Android 2.1 - 3.x */
Unknown directive
236
-moz-box-sizing: border-box; /* Firefox 1 - 28 */
Unknown directive
237
box-sizing: border-box;
Unknown directive
238
width: 50%;
Unknown directive
239
padding: 0px;
Unknown directive
240
margin: 0 0px 1px 0;
Unknown directive
241
border-right: 1px solid white;
Unknown directive
242
}
Syntax not understood
244
.nav_item:nth-child(2n){
Unknown directive
245
border-right: none;
Unknown directive
247
}
Syntax not understood
248
}
Syntax not understood
250
@media only screen and (min-width:1px) and (max-width:319px) {
Unknown directive
251
.wrapper {
Syntax not understood
252
width: 100%;
Unknown directive
253
}
Syntax not understood
255
.content_image {
Syntax not understood
256
display: none;
Unknown directive
257
}
Syntax not understood
259
h1.header_headline span{
Syntax not understood
260
display: none;
Unknown directive
261
}
Syntax not understood
263
h1.header_headline:before {
Unknown directive
264
content: 'Shoes & Fashion';
Unknown directive
265
}
Syntax not understood
267
UL.nav {
Syntax not understood
268
width: 100%;
Unknown directive
269
}
Syntax not understood
271
.nav_item {
Syntax not understood
273
width: 100%;
Unknown directive
274
padding: 0px;
Unknown directive
275
margin: 0 0px 1px 0;
Unknown directive
276
}
Syntax not understood
279
}
Syntax not understood
282
</style>
Syntax not understood
283
<link rel="icon" href="//media.ztat.net/media/landingpage/fallback/zalando.ico" type="image/x-icon">
Syntax not understood
284
</head>
Syntax not understood
285
<body>
Syntax not understood
287
<div class="wrapper wrapper_header header">
Syntax not understood
288
<img class="header_image" src="//skin.ztat.net/s/tir/zalando/img/MAIN/logos/shops/schuhe.jpg" width="190"
Syntax not understood
289
height="53"
Syntax not understood
290
alt="Shoes and fashion online with free shipping by zalando"
Syntax not understood
291
title="Shoes and fashion online with free shipping by zalando">
Syntax not understood
293
<h1 class="header_headline"><span>Shoes &amp; Fashion online - Zalando is available in the following
Syntax not understood
294
countries</span></h1>
Syntax not understood
295
</div>
Syntax not understood
297
<div class="wrapper wrapper_content content">
Syntax not understood
298
<img src="//a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg" width="455px"
Syntax not understood
299
height="399px" alt="Zalando - Shoes &amp; Fashion online" class="content_image">
Syntax not understood
300
<ul class="content_nav-wrapper nav">
Syntax not understood
301
<li class="nav_item">
Syntax not understood
302
<a class="nav_link nav_link-de" href="https://zalando.de/">Zalando.de</a>
Unknown directive
303
</li>
Syntax not understood
304
<li class="nav_item">
Syntax not understood
305
<a class="nav_link nav_link-fr" href="https://www.zalando.fr/">Zalando.fr</a>
Unknown directive
306
</li>
Syntax not understood
307
<li class="nav_item">
Syntax not understood
308
<a class="nav_link nav_link-lu" href="https://zalando.lu/">Zalando.lu</a>
Unknown directive
309
</li>
Syntax not understood
310
<li class="nav_item">
Syntax not understood
311
<a class="nav_link nav_link-at" href="https://www.zalando.at/">Zalando.at</a>
Unknown directive
312
</li>
Syntax not understood
313
<li class="nav_item">
Syntax not understood
314
<a class="nav_link nav_link-it" href="https://www.zalando.it/">Zalando.it</a>
Unknown directive
315
</li>
Syntax not understood
316
<li class="nav_item">
Syntax not understood
317
<a class="nav_link nav_link-no" href="https://www.zalando.no/">Zalando.no</a>
Unknown directive
318
</li>
Syntax not understood
319
<li class="nav_item">
Syntax not understood
320
<a class="nav_link nav_link-ch" href="https://www.zalando.ch/">Zalando.ch</a>
Unknown directive
321
</li>
Syntax not understood
322
<li class="nav_item">
Syntax not understood
323
<a class="nav_link nav_link-es" href="https://www.zalando.es/">Zalando.es</a>
Unknown directive
324
</li>
Syntax not understood
325
<li class="nav_item">
Syntax not understood
326
<a class="nav_link nav_link-se" href="https://www.zalando.se/">Zalando.se</a>
Unknown directive
327
</li>
Syntax not understood
328
<li class="nav_item">
Syntax not understood
329
<a class="nav_link nav_link-gb" href="https://www.zalando.co.uk/">Zalando.uk</a>
Unknown directive
330
</li>
Syntax not understood
331
<li class="nav_item">
Syntax not understood
332
<a class="nav_link nav_link-nl" href="https://www.zalando.nl/">Zalando.nl</a>
Unknown directive
333
</li>
Syntax not understood
334
<li class="nav_item">
Syntax not understood
335
<a class="nav_link nav_link-dk" href="https://www.zalando.dk/">Zalando.dk</a>
Unknown directive
336
</li>
Syntax not understood
337
<li class="nav_item">
Syntax not understood
338
<a class="nav_link nav_link-pl" href="https://www.zalando.pl/">Zalando.pl</a>
Unknown directive
339
</li>
Syntax not understood
340
<li class="nav_item">
Syntax not understood
341
<a class="nav_link nav_link-be" href="https://www.zalando.be/">Zalando.be</a>
Unknown directive
342
</li>
Syntax not understood
343
<li class="nav_item">
Syntax not understood
344
<a class="nav_link nav_link-fi" href="https://www.zalando.fi/">Zalando.fi</a>
Unknown directive
345
</li>
Syntax not understood
346
<li class="nav_item">
Syntax not understood
347
<a class="nav_link2 nav_link-cz" href="https://www.zalando.cz/">Zalando.cz</a>
Unknown directive
348
</li>
Syntax not understood
349
<li class="nav_item">
Syntax not understood
350
<a class="nav_link2 nav_link-ie" href="https://www.zalando.ie/">Zalando.ie</a>
Unknown directive
351
</li>
Syntax not understood
352
</ul>
Syntax not understood
353
</div>
Syntax not understood
354
<div class="wrapper wrapper_footer footer">
Syntax not understood
355
<a class="footer_link" href="http://www.zalando.de/zalando-impressum/">Legal notice</a>
Unknown directive
356
</div>
Syntax not understood
358
<script>
Syntax not understood
359
(function () {
Syntax not understood
362
var country;
Syntax not understood
364
function alertInhalt() {
Syntax not understood
366
if (http_request.readyState == 4) {
Syntax not understood
367
if (!this.status || this.status == 200) {
Syntax not understood
368
var respJSON = JSON.parse(this.responseText);
Syntax not understood
369
country = respJSON["countryCode"].toLowerCase();
Syntax not understood
370
redirect(country);
Syntax not understood
371
} else {
Syntax not understood
372
alert('Bei dem Request ist ein Problem aufgetreten.');
Syntax not understood
373
}
Syntax not understood
374
}
Syntax not understood
375
return true;
Syntax not understood
376
}
Syntax not understood
378
if (navigator.userAgent.search('MSIE') < 0 && window.XMLHttpRequest) { // Mozilla, Safari, ...
Syntax not understood
379
var http_request = new XMLHttpRequest();
Syntax not understood
380
http_request.onreadystatechange = alertInhalt;
Syntax not understood
381
http_request.open('GET', "//ip-api.com/json/?fields=country,countryCode", true);
Syntax not understood
382
http_request.send(null);
Syntax not understood
383
} else {
Syntax not understood
384
var xdr = new XDomainRequest();
Syntax not understood
385
xdr.open("get", "//ip-api.com/json/?fields=country,countryCode");
Syntax not understood
386
xdr.onload = function () {
Syntax not understood
387
var response = xdr.responseText;
Syntax not understood
388
var respJSON_IE = JSON.parse(this.responseText);
Syntax not understood
389
country = respJSON["countryCode"].toLowerCase();
Syntax not understood
390
redirect(country);
Syntax not understood
391
};
Syntax not understood
392
xdr.onprogress = function () {
Syntax not understood
393
};
Syntax not understood
394
xdr.ontimeout = function () {
Syntax not understood
395
};
Syntax not understood
396
xdr.onerror = function () {
Syntax not understood
397
};
Syntax not understood
398
setTimeout(function () {
Syntax not understood
399
xdr.send();
Syntax not understood
400
}, 0);
Syntax not understood
401
}
Syntax not understood
403
function redirect(country) {
Syntax not understood
405
if (country.length > 0 && country != null && country != undefined) {
Syntax not understood
407
switch (country) {
Syntax not understood
408
case 'de':
Unknown directive
409
document.location = "//www.zalando.de";
Syntax not understood
410
break;
Syntax not understood
411
case 'at':
Unknown directive
412
document.location = "//www.zalando.at";
Syntax not understood
413
break;
Syntax not understood
414
case 'ch':
Unknown directive
415
document.location = "//www.zalando.ch";
Syntax not understood
416
break;
Syntax not understood
417
case 'nl':
Unknown directive
418
document.location = "//www.zalando.nl";
Syntax not understood
419
break;
Syntax not understood
420
case 'fr':
Unknown directive
421
document.location = "//www.zalando.fr";
Syntax not understood
422
break;
Syntax not understood
423
case 'gb':
Unknown directive
424
document.location = "//www.zalando.co.uk";
Syntax not understood
425
break;
Syntax not understood
426
case 'it':
Unknown directive
427
document.location = "//www.zalando.it";
Syntax not understood
428
break;
Syntax not understood
429
case 'be':
Unknown directive
430
document.location = "//www.zalando.be";
Syntax not understood
431
break;
Syntax not understood
432
case 'es':
Unknown directive
433
document.location = "//www.zalando.es";
Syntax not understood
434
break;
Syntax not understood
435
case 'se':
Unknown directive
436
document.location = "//www.zalando.se";
Syntax not understood
437
break;
Syntax not understood
438
case 'dk':
Unknown directive
439
document.location = "//www.zalando.dk";
Syntax not understood
440
break;
Syntax not understood
441
case 'fi':
Unknown directive
442
document.location = "//www.zalando.fi";
Syntax not understood
443
break;
Syntax not understood
444
case 'no':
Unknown directive
445
document.location = "//www.zalando.no";
Syntax not understood
446
break;
Syntax not understood
447
case 'pl':
Unknown directive
448
document.location = "//www.zalando.pl";
Syntax not understood
449
break;
Syntax not understood
450
case 'lu':
Unknown directive
451
document.location = "//www.zalando.lu";
Syntax not understood
452
break;
Syntax not understood
453
}
Syntax not understood
455
} else {
Syntax not understood
456
return false;
Syntax not understood
457
}
Syntax not understood
458
return true;
Syntax not understood
460
}
Syntax not understood
461
})();
Syntax not understood
462
</script>
Syntax not understood
463
</body>
Syntax not understood
464
</html>
Syntax not understood

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 zalando.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 zalando.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) 80
Performance 94
Accessibility 100
Best Practices 80
SEO 85
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://zalando.com/
Updated: 1st April, 2021

0.82 seconds
First Contentful Paint (FCP)
82%
16%
2%

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

Simulate loading on mobile
94

Performance

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

Metrics

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

Other

First CPU Idle — 2.4 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 2.0 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 zalando.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://zalando.com/
http/1.1
0
118.51699976251
233
0
301
text/html
https://zalando.com/
h2
119.30399993435
268.7909998931
3391
16397
200
text/html
Document
https://skin.ztat.net/s/tir/zalando/img/MAIN/logos/shops/schuhe.jpg
http/1.1
316.50900002569
497.18399997801
6740
6356
200
image/jpeg
Image
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
h2
316.75199978054
496.37300008908
64660
64204
200
image/jpeg
Image
https://ip-api.com/json/?fields=country,countryCode
http/1.1
321.90399989486
404.39900010824
184
2
403
application/json
XHR
https://skin2.ztat.net/s/tir/zalando/img/MAIN/sprites/spriteIcon.png
http/1.1
364.38299994916
499.41899999976
89942
89734
200
image/png
Image
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo400.woff
h2
389.95900005102
497.85599997267
14234
13776
200
application/font-woff
Font
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo700.woff
h2
393.60200008377
498.92899999395
14275
13816
200
application/font-woff
Font
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)
474.161
23.761
504.888
65.852
570.762
41.535
612.776
36.026
648.948
48.627
706.314
57.944
765.264
8.558
773.985
13.096
1867.915
5.032
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Zalando.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Zalando.com should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 63 KiB
Time to Interactive can be slowed down by resources on the page. Zalando.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
64204
64204
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Zalando.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Zalando.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Zalando.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 150 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://zalando.com/
150.484
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Zalando.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://zalando.com/
630
https://zalando.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Zalando.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.
URL Potential Savings (Ms)
https://skin.ztat.net/s/tir/zalando/img/MAIN/logos/shops/schuhe.jpg
0

Diagnostics

Avoids enormous network payloads — Total size was 189 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://skin2.ztat.net/s/tir/zalando/img/MAIN/sprites/spriteIcon.png
89942
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
64660
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo700.woff
14275
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo400.woff
14234
https://skin.ztat.net/s/tir/zalando/img/MAIN/logos/shops/schuhe.jpg
6740
https://zalando.com/
3391
http://zalando.com/
233
https://ip-api.com/json/?fields=country,countryCode
184
Avoids an excessive DOM size — 44 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
44
Maximum DOM Depth
ZALANDO.DE
5
Maximum Child Elements
ZALANDO.DE ZALANDO.FR ZALANDO.LU ZALANDO.AT ZALANDO.IT ZALANDO.NO ZALANDO.CH ZA…
17
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Zalando.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.4 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://zalando.com/
1198.18
323.892
12.964
Unattributable
89.164
19.192
0.604
Minimizes main-thread work — 1.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)
Style & Layout
595.556
Script Evaluation
343.084
Other
220.068
Rendering
95.86
Parse HTML & CSS
19.208
Script Parsing & Compilation
13.568
Keep request counts low and transfer sizes small — 8 requests • 189 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
8
193659
Image
3
161342
Font
2
28509
Document
1
3391
Other
2
417
Stylesheet
0
0
Media
0
0
Script
0
0
Third-party
6
190035
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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
Shoes and fashion online with free shipping by zalando
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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://zalando.com/
1220
263
https://zalando.com/
2263
195
https://zalando.com/
1483
144
https://zalando.com/
1627
116
https://zalando.com/
1110
95
https://zalando.com/
630
83
https://zalando.com/
713
52
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

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

Other

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

Opportunities

Efficiently encode images — Potential savings of 15 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
64204
15183
Serve images in next-gen formats — Potential savings of 97 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://skin2.ztat.net/s/tir/zalando/img/MAIN/sprites/spriteIcon.png
89734
63596
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
64204
35910

Diagnostics

Serve static assets with an efficient cache policy — 5 resources found
Zalando.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://skin2.ztat.net/s/tir/zalando/img/MAIN/sprites/spriteIcon.png
0
89942
https://a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg
0
64660
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo700.woff
0
14275
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo400.woff
0
14234
https://skin.ztat.net/s/tir/zalando/img/MAIN/logos/shops/schuhe.jpg
0
6740
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://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo400.woff
107.89699992165
https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo700.woff
105.32699991018
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of zalando.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

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

Internationalization and localization

`<html>` element has a `[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"]`
Zalando.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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 zalando.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
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.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://skin.ztat.net/s/tir/zalando/img/MAIN/logos/shops/schuhe.jpg
190 x 53
190 x 53
380 x 106

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
SHOW DETAILS
Failed to load resource: the server responded with a status of 403 (Forbidden)
85

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for zalando.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 zalando.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.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

robots.txt is not valid — 393 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!doctype html>
Syntax not understood
2
<html lang="en">
Syntax not understood
3
<head profile="http://gmpg.org/xfn/11">
Unknown directive
4
<meta charset="UTF-8">
Syntax not understood
5
<title>Zalando - Shoes and Fashion Online</title>
Syntax not understood
7
<meta name="description" content="Zalando | Buy shoes online: Shoes from top brands.">
Unknown directive
8
<meta name="viewport" content="width=device-width, initial-scale=1">
Syntax not understood
9
<meta name="google-site-verification" content="1VHp1WET1lNXsSv7mKcEhpcru_SHBd_VRYBP5cUBWUY">
Syntax not understood
10
<style>
Syntax not understood
15
@font-face {
Syntax not understood
16
font-family: Arimo;
Unknown directive
17
font-style: normal;
Unknown directive
18
font-weight: 400;
Unknown directive
19
src: url('https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo400.woff');
Unknown directive
20
}
Syntax not understood
22
@font-face {
Syntax not understood
23
font-family: 'Arimo';
Unknown directive
24
font-style: normal;
Unknown directive
25
font-weight: 700;
Unknown directive
26
src: url('https://secure-skin.ztat.net/s/qsk/zalando/fonts/COMMON/arimo700.woff');
Unknown directive
27
}
Syntax not understood
29
.wrapper {
Syntax not understood
30
font-family: Arimo, Arial, Helvetica, "DejaVu Sans", "Arial Unicode MS", "Lucida Sans Unicode",
Unknown directive
31
sans-serif;
Syntax not understood
32
margin: 0 auto;
Unknown directive
33
width: 1010px;
Unknown directive
34
}
Syntax not understood
36
.header_headline {
Syntax not understood
37
background: #999999;
Unknown directive
38
color: #ffffff;
Unknown directive
39
font-size: 18px;
Unknown directive
40
font-weight: 500;
Unknown directive
41
letter-spacing: 2px;
Unknown directive
42
line-height: 44px;
Unknown directive
43
margin: 11px 0 0 0;
Unknown directive
44
padding: 0;
Unknown directive
45
text-transform: uppercase;
Unknown directive
46
text-align: center;
Unknown directive
48
}
Syntax not understood
50
.content {
Syntax not understood
51
margin-top: 1px;
Unknown directive
52
overflow: hidden;
Unknown directive
53
}
Syntax not understood
55
.content_image {
Syntax not understood
56
float: left;
Unknown directive
57
height: 399px;
Unknown directive
58
width: 457px;
Unknown directive
59
}
Syntax not understood
61
.nav {
Syntax not understood
62
float: left;
Unknown directive
63
list-style-type: none;
Unknown directive
64
overflow: hidden;
Unknown directive
65
margin: 0;
Unknown directive
66
padding: 0;
Unknown directive
67
width: 553px;
Unknown directive
68
}
Syntax not understood
70
.nav_item {
Syntax not understood
71
display: table;
Unknown directive
72
float: left;
Unknown directive
73
height: 79px;
Unknown directive
74
margin: 0 0 1px 1px;
Unknown directive
75
position: relative;
Unknown directive
76
width: 183px;
Unknown directive
77
}
Syntax not understood
79
.nav_link, .nav_link2 {
Syntax not understood
80
background-color: #f3f3f3;
Unknown directive
81
color: #404040;
Unknown directive
82
display: table-cell;
Unknown directive
83
font-size: 10px;
Unknown directive
84
font-weight: bold;
Unknown directive
85
letter-spacing: .2em;
Unknown directive
86
text-align: center;
Unknown directive
87
text-decoration: none;
Unknown directive
88
text-transform: uppercase;
Unknown directive
89
vertical-align: middle;
Unknown directive
90
width: 100%;
Unknown directive
91
}
Syntax not understood
93
.nav_link:hover, .nav_link2:hover{
Unknown directive
94
background-color: #ddd;
Unknown directive
95
}
Syntax not understood
97
.nav_link:before {
Unknown directive
98
background-image: url("//skin2.ztat.net/s/tir/zalando/img/MAIN/sprites/spriteIcon.png");
Unknown directive
99
background-repeat: no-repeat;
Unknown directive
100
content: '';
Unknown directive
101
display: inline-block;
Unknown directive
102
height: 15px;
Unknown directive
103
margin: 0 20px 0 0;
Unknown directive
104
vertical-align: -4px;
Unknown directive
105
width: 24px;
Unknown directive
106
}
Syntax not understood
108
.nav_link-cz:before {
Unknown directive
109
background-image: url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' version='1.0' width='24' height='18'><rect width='24' height='18' fill='#d7141a'/><rect width='24' height='9' fill='#fff'/><path d='M 12,9 0,0 V 18 z' fill='#11457e'/></svg>");
Unknown directive
111
background-repeat: no-repeat;
Unknown directive
112
content: '';
Unknown directive
113
display: inline-block;
Unknown directive
114
height: 15px;
Unknown directive
115
margin: 0 20px 0 0;
Unknown directive
116
vertical-align: -4px;
Unknown directive
117
width: 24px;
Unknown directive
118
}
Syntax not understood
120
.nav_link-ie:before {
Unknown directive
121
background-image: url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' width='24' height='18'><rect fill='#169b62' width='8' height='18' x='0'/><rect fill='#fff' width='8' height='18' x='8'/><rect fill='#ff883e' x='16' width='8' height='18'/></svg>");
Unknown directive
123
background-repeat: no-repeat;
Unknown directive
124
content: '';
Unknown directive
125
display: inline-block;
Unknown directive
126
height: 15px;
Unknown directive
127
margin: 0 20px 0 0;
Unknown directive
128
vertical-align: -4px;
Unknown directive
129
width: 24px;
Unknown directive
130
}
Syntax not understood
132
.nav_link-de:before {
Unknown directive
133
background-position: 0 0;
Unknown directive
134
}
Syntax not understood
136
.nav_link-nl:before {
Unknown directive
137
background-position: -28px 0;
Unknown directive
138
}
Syntax not understood
140
.nav_link-ch:before {
Unknown directive
141
background-position: -190px 0;
Unknown directive
142
}
Syntax not understood
144
.nav_link-fr:before {
Unknown directive
145
background-position: -55px 0;
Unknown directive
146
}
Syntax not understood
148
.nav_link-be:before {
Unknown directive
149
background-position: -82px 0;
Unknown directive
150
}
Syntax not understood
152
.nav_link-lu:before {
Unknown directive
153
background-position: -268px 0;
Unknown directive
154
}
Syntax not understood
156
.nav_link-at:before {
Unknown directive
157
background-position: -109px 0;
Unknown directive
158
}
Syntax not understood
160
.nav_link-it:before {
Unknown directive
161
background-position: -136px 0;
Unknown directive
162
}
Syntax not understood
164
.nav_link-gb:before {
Unknown directive
165
background-position: -163px 0;
Unknown directive
166
}
Syntax not understood
168
.nav_link-es:before {
Unknown directive
169
background-position: -294px 0;
Unknown directive
170
}
Syntax not understood
172
.nav_link-fi:before {
Unknown directive
173
background-position: -216px 0;
Unknown directive
174
}
Syntax not understood
176
.nav_link-no:before {
Unknown directive
177
background-position: -372px 0;
Unknown directive
178
}
Syntax not understood
180
.nav_link-se:before {
Unknown directive
181
background-position: -320px 0;
Unknown directive
182
}
Syntax not understood
184
.nav_link-pl:before {
Unknown directive
185
background-position: -346px 0;
Unknown directive
186
}
Syntax not understood
188
.nav_link-dk:before {
Unknown directive
189
background-position: -242px 0;
Unknown directive
190
}
Syntax not understood
192
.footer {
Syntax not understood
193
text-align: right;
Unknown directive
194
margin-top: 4px;
Unknown directive
195
}
Syntax not understood
197
.footer_link {
Syntax not understood
198
color: #000;
Unknown directive
199
font-size: 12px;
Unknown directive
200
text-decoration: none;
Unknown directive
201
}
Syntax not understood
203
*+html .nav_link {
Syntax not understood
204
display: block;
Unknown directive
205
height: 48px;
Unknown directive
206
padding-top: 31px;
Unknown directive
207
}
Syntax not understood
209
@media only screen and (min-width:320px) and (max-width:640px){
Unknown directive
210
.wrapper {
Syntax not understood
211
width: 100%;
Unknown directive
212
}
Syntax not understood
214
.content_image {
Syntax not understood
215
display: none;
Unknown directive
216
}
Syntax not understood
218
h1.header_headline span{
Syntax not understood
219
display: none;
Unknown directive
220
}
Syntax not understood
222
h1.header_headline:before {
Unknown directive
223
content: 'Zalando is available in:';
Unknown directive
224
}
Syntax not understood
226
UL.nav {
Syntax not understood
227
width: 100%;
Unknown directive
228
}
Syntax not understood
230
.nav_item {
Syntax not understood
231
-webkit-box-flex: 1;
Unknown directive
232
-webkit-flex-grow: 1;
Unknown directive
233
-ms-flex-positive: 1;
Unknown directive
234
flex-grow: 1;
Unknown directive
235
-webkit-box-sizing: border-box; /* Safari 3.0 - 5.0, Chrome 1 - 9, Android 2.1 - 3.x */
Unknown directive
236
-moz-box-sizing: border-box; /* Firefox 1 - 28 */
Unknown directive
237
box-sizing: border-box;
Unknown directive
238
width: 50%;
Unknown directive
239
padding: 0px;
Unknown directive
240
margin: 0 0px 1px 0;
Unknown directive
241
border-right: 1px solid white;
Unknown directive
242
}
Syntax not understood
244
.nav_item:nth-child(2n){
Unknown directive
245
border-right: none;
Unknown directive
247
}
Syntax not understood
248
}
Syntax not understood
250
@media only screen and (min-width:1px) and (max-width:319px) {
Unknown directive
251
.wrapper {
Syntax not understood
252
width: 100%;
Unknown directive
253
}
Syntax not understood
255
.content_image {
Syntax not understood
256
display: none;
Unknown directive
257
}
Syntax not understood
259
h1.header_headline span{
Syntax not understood
260
display: none;
Unknown directive
261
}
Syntax not understood
263
h1.header_headline:before {
Unknown directive
264
content: 'Shoes & Fashion';
Unknown directive
265
}
Syntax not understood
267
UL.nav {
Syntax not understood
268
width: 100%;
Unknown directive
269
}
Syntax not understood
271
.nav_item {
Syntax not understood
273
width: 100%;
Unknown directive
274
padding: 0px;
Unknown directive
275
margin: 0 0px 1px 0;
Unknown directive
276
}
Syntax not understood
279
}
Syntax not understood
282
</style>
Syntax not understood
283
<link rel="icon" href="//media.ztat.net/media/landingpage/fallback/zalando.ico" type="image/x-icon">
Syntax not understood
284
</head>
Syntax not understood
285
<body>
Syntax not understood
287
<div class="wrapper wrapper_header header">
Syntax not understood
288
<img class="header_image" src="//skin.ztat.net/s/tir/zalando/img/MAIN/logos/shops/schuhe.jpg" width="190"
Syntax not understood
289
height="53"
Syntax not understood
290
alt="Shoes and fashion online with free shipping by zalando"
Syntax not understood
291
title="Shoes and fashion online with free shipping by zalando">
Syntax not understood
293
<h1 class="header_headline"><span>Shoes &amp; Fashion online - Zalando is available in the following
Syntax not understood
294
countries</span></h1>
Syntax not understood
295
</div>
Syntax not understood
297
<div class="wrapper wrapper_content content">
Syntax not understood
298
<img src="//a1276.ztat.net/lpo/zalando/lp/2014/07/lpo-6644/default_landing_jul_15.jpg" width="455px"
Syntax not understood
299
height="399px" alt="Zalando - Shoes &amp; Fashion online" class="content_image">
Syntax not understood
300
<ul class="content_nav-wrapper nav">
Syntax not understood
301
<li class="nav_item">
Syntax not understood
302
<a class="nav_link nav_link-de" href="https://zalando.de/">Zalando.de</a>
Unknown directive
303
</li>
Syntax not understood
304
<li class="nav_item">
Syntax not understood
305
<a class="nav_link nav_link-fr" href="https://www.zalando.fr/">Zalando.fr</a>
Unknown directive
306
</li>
Syntax not understood
307
<li class="nav_item">
Syntax not understood
308
<a class="nav_link nav_link-lu" href="https://zalando.lu/">Zalando.lu</a>
Unknown directive
309
</li>
Syntax not understood
310
<li class="nav_item">
Syntax not understood
311
<a class="nav_link nav_link-at" href="https://www.zalando.at/">Zalando.at</a>
Unknown directive
312
</li>
Syntax not understood
313
<li class="nav_item">
Syntax not understood
314
<a class="nav_link nav_link-it" href="https://www.zalando.it/">Zalando.it</a>
Unknown directive
315
</li>
Syntax not understood
316
<li class="nav_item">
Syntax not understood
317
<a class="nav_link nav_link-no" href="https://www.zalando.no/">Zalando.no</a>
Unknown directive
318
</li>
Syntax not understood
319
<li class="nav_item">
Syntax not understood
320
<a class="nav_link nav_link-ch" href="https://www.zalando.ch/">Zalando.ch</a>
Unknown directive
321
</li>
Syntax not understood
322
<li class="nav_item">
Syntax not understood
323
<a class="nav_link nav_link-es" href="https://www.zalando.es/">Zalando.es</a>
Unknown directive
324
</li>
Syntax not understood
325
<li class="nav_item">
Syntax not understood
326
<a class="nav_link nav_link-se" href="https://www.zalando.se/">Zalando.se</a>
Unknown directive
327
</li>
Syntax not understood
328
<li class="nav_item">
Syntax not understood
329
<a class="nav_link nav_link-gb" href="https://www.zalando.co.uk/">Zalando.uk</a>
Unknown directive
330
</li>
Syntax not understood
331
<li class="nav_item">
Syntax not understood
332
<a class="nav_link nav_link-nl" href="https://www.zalando.nl/">Zalando.nl</a>
Unknown directive
333
</li>
Syntax not understood
334
<li class="nav_item">
Syntax not understood
335
<a class="nav_link nav_link-dk" href="https://www.zalando.dk/">Zalando.dk</a>
Unknown directive
336
</li>
Syntax not understood
337
<li class="nav_item">
Syntax not understood
338
<a class="nav_link nav_link-pl" href="https://www.zalando.pl/">Zalando.pl</a>
Unknown directive
339
</li>
Syntax not understood
340
<li class="nav_item">
Syntax not understood
341
<a class="nav_link nav_link-be" href="https://www.zalando.be/">Zalando.be</a>
Unknown directive
342
</li>
Syntax not understood
343
<li class="nav_item">
Syntax not understood
344
<a class="nav_link nav_link-fi" href="https://www.zalando.fi/">Zalando.fi</a>
Unknown directive
345
</li>
Syntax not understood
346
<li class="nav_item">
Syntax not understood
347
<a class="nav_link2 nav_link-cz" href="https://www.zalando.cz/">Zalando.cz</a>
Unknown directive
348
</li>
Syntax not understood
349
<li class="nav_item">
Syntax not understood
350
<a class="nav_link2 nav_link-ie" href="https://www.zalando.ie/">Zalando.ie</a>
Unknown directive
351
</li>
Syntax not understood
352
</ul>
Syntax not understood
353
</div>
Syntax not understood
354
<div class="wrapper wrapper_footer footer">
Syntax not understood
355
<a class="footer_link" href="http://www.zalando.de/zalando-impressum/">Legal notice</a>
Unknown directive
356
</div>
Syntax not understood
358
<script>
Syntax not understood
359
(function () {
Syntax not understood
362
var country;
Syntax not understood
364
function alertInhalt() {
Syntax not understood
366
if (http_request.readyState == 4) {
Syntax not understood
367
if (!this.status || this.status == 200) {
Syntax not understood
368
var respJSON = JSON.parse(this.responseText);
Syntax not understood
369
country = respJSON["countryCode"].toLowerCase();
Syntax not understood
370
redirect(country);
Syntax not understood
371
} else {
Syntax not understood
372
alert('Bei dem Request ist ein Problem aufgetreten.');
Syntax not understood
373
}
Syntax not understood
374
}
Syntax not understood
375
return true;
Syntax not understood
376
}
Syntax not understood
378
if (navigator.userAgent.search('MSIE') < 0 && window.XMLHttpRequest) { // Mozilla, Safari, ...
Syntax not understood
379
var http_request = new XMLHttpRequest();
Syntax not understood
380
http_request.onreadystatechange = alertInhalt;
Syntax not understood
381
http_request.open('GET', "//ip-api.com/json/?fields=country,countryCode", true);
Syntax not understood
382
http_request.send(null);
Syntax not understood
383
} else {
Syntax not understood
384
var xdr = new XDomainRequest();
Syntax not understood
385
xdr.open("get", "//ip-api.com/json/?fields=country,countryCode");
Syntax not understood
386
xdr.onload = function () {
Syntax not understood
387
var response = xdr.responseText;
Syntax not understood
388
var respJSON_IE = JSON.parse(this.responseText);
Syntax not understood
389
country = respJSON["countryCode"].toLowerCase();
Syntax not understood
390
redirect(country);
Syntax not understood
391
};
Syntax not understood
392
xdr.onprogress = function () {
Syntax not understood
393
};
Syntax not understood
394
xdr.ontimeout = function () {
Syntax not understood
395
};
Syntax not understood
396
xdr.onerror = function () {
Syntax not understood
397
};
Syntax not understood
398
setTimeout(function () {
Syntax not understood
399
xdr.send();
Syntax not understood
400
}, 0);
Syntax not understood
401
}
Syntax not understood
403
function redirect(country) {
Syntax not understood
405
if (country.length > 0 && country != null && country != undefined) {
Syntax not understood
407
switch (country) {
Syntax not understood
408
case 'de':
Unknown directive
409
document.location = "//www.zalando.de";
Syntax not understood
410
break;
Syntax not understood
411
case 'at':
Unknown directive
412
document.location = "//www.zalando.at";
Syntax not understood
413
break;
Syntax not understood
414
case 'ch':
Unknown directive
415
document.location = "//www.zalando.ch";
Syntax not understood
416
break;
Syntax not understood
417
case 'nl':
Unknown directive
418
document.location = "//www.zalando.nl";
Syntax not understood
419
break;
Syntax not understood
420
case 'fr':
Unknown directive
421
document.location = "//www.zalando.fr";
Syntax not understood
422
break;
Syntax not understood
423
case 'gb':
Unknown directive
424
document.location = "//www.zalando.co.uk";
Syntax not understood
425
break;
Syntax not understood
426
case 'it':
Unknown directive
427
document.location = "//www.zalando.it";
Syntax not understood
428
break;
Syntax not understood
429
case 'be':
Unknown directive
430
document.location = "//www.zalando.be";
Syntax not understood
431
break;
Syntax not understood
432
case 'es':
Unknown directive
433
document.location = "//www.zalando.es";
Syntax not understood
434
break;
Syntax not understood
435
case 'se':
Unknown directive
436
document.location = "//www.zalando.se";
Syntax not understood
437
break;
Syntax not understood
438
case 'dk':
Unknown directive
439
document.location = "//www.zalando.dk";
Syntax not understood
440
break;
Syntax not understood
441
case 'fi':
Unknown directive
442
document.location = "//www.zalando.fi";
Syntax not understood
443
break;
Syntax not understood
444
case 'no':
Unknown directive
445
document.location = "//www.zalando.no";
Syntax not understood
446
break;
Syntax not understood
447
case 'pl':
Unknown directive
448
document.location = "//www.zalando.pl";
Syntax not understood
449
break;
Syntax not understood
450
case 'lu':
Unknown directive
451
document.location = "//www.zalando.lu";
Syntax not understood
452
break;
Syntax not understood
453
}
Syntax not understood
455
} else {
Syntax not understood
456
return false;
Syntax not understood
457
}
Syntax not understood
458
return true;
Syntax not understood
460
}
Syntax not understood
461
})();
Syntax not understood
462
</script>
Syntax not understood
463
</body>
Syntax not understood
464
</html>
Syntax not understood

Mobile Friendly

Document doesn't use legible font sizes — 17.48% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
SHOW DETAILS
.nav_link, .nav_link2
82.52%
10px
SHOW DETAILS
17.48%
≥ 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.
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 zalando.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 zalando.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: 130.211.9.113
Continent: North America
Country: United States
United States Flag
Region: California
City: Mountain View
Longitude: -122.0775
Latitude: 37.4056
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Google LLC
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
Key-Systems GmbH 18.185.15.158
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 3.7/5 (2 reviews)
WOT Trustworthiness: 74/100
WOT Child Safety: 96/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.zalando.com
Issued By: Sectigo RSA Domain Validation Secure Server CA
Valid From: 27th November, 2019
Valid To: 26th November, 2021
Subject: CN = *.zalando.com
Hash: adf9bc85
Issuer: CN = Sectigo RSA Domain Validation Secure Server CA
O = Sectigo Limited
S = GB
Version: 2
Serial Number: 0xB6C2F56BC6D0D1EADBD242F4EB36C3C6
Serial Number (Hex): B6C2F56BC6D0D1EADBD242F4EB36C3C6
Valid From: 27th November, 2024
Valid To: 26th November, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.7
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1
Authority Information Access: CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP - URI:http://ocsp.sectigo.com
SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Nov 27 10:53:53.081 2019 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:1C:0C:1D:0D:57:86:72:40:60:FF:2E:1D:
38:8D:94:72:D3:8C:4F:05:93:BD:FF:C0:C5:84:1A:A6:
D6:E7:33:74:02:20:5A:3E:0E:58:53:EA:14:76:D4:90:
12:0A:4A:09:3F:46:27:4C:C1:BC:B4:15:22:15:30:F5:
CC:6A:86:79:FD:1E
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
Timestamp : Nov 27 10:53:53.058 2019 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:27:00:0B:3C:BE:39:37:EC:89:E6:45:04:
A3:8A:4E:BB:A0:40:41:7D:55:75:E3:C7:0B:CB:1B:45:
05:83:CD:32:02:21:00:A2:42:CA:6B:A7:B6:ED:78:CE:
FA:36:42:53:56:81:3D:00:26:5B:19:51:BC:14:09:EC:
28:18:3B:1F:24:D9:ED
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Nov 27 10:53:53.175 2019 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:E1:18:A6:57:D6:49:16:5E:35:4B:46:
AF:80:C4:79:00:72:2E:4B:79:73:C7:F8:3A:FD:4F:04:
1E:BB:36:5E:3D:02:20:06:F3:8B:A6:8B:33:01:0E:50:
F1:C1:87:B0:AE:15:B4:55:CB:13:3A:E5:A7:75:0D:2A:
EE:02:58:FB:63:D7:A0
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:zalando.com
DNS:*.zalando.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
zalando.com. 130.211.9.113 IN 299

NS Records

Host Nameserver Class TTL
zalando.com. ns-1028.awsdns-00.org. IN 299
zalando.com. ns-1725.awsdns-23.co.uk. IN 299
zalando.com. ns-674.awsdns-20.net. IN 299
zalando.com. ns-70.awsdns-08.com. IN 299

AAAA Records

IP Address Class TTL
2600:1901:0:62af:: IN 299

MX Records

Priority Host Server Class TTL
1 zalando.com. aspmx.l.google.com. IN 3599
10 zalando.com. alt3.aspmx.l.google.com. IN 3599
10 zalando.com. alt4.aspmx.l.google.com. IN 3599
5 zalando.com. alt1.aspmx.l.google.com. IN 3599
5 zalando.com. alt2.aspmx.l.google.com. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
zalando.com. ns-1028.awsdns-00.org. awsdns-hostmaster.amazon.com. 899

TXT Records

Host Value Class TTL
zalando.com. MS=ms31863815 IN 3599
zalando.com. facebook-domain-verification=91v041mbqqze167es1w24ja4qj96h5 IN 3599
zalando.com. google-site-verification=BER9CXK3xkVm2RqIvjSNn7Uqnl29B0xVywNcMd4xwrg IN 3599
zalando.com. v=spf1 IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 1st April, 2021
Content-Type: text/html
Content-Length: 16397
Last-Modified: 31st March, 2021
Vary: Accept-Encoding
ETag: "60645598-400d"
Accept-Ranges: bytes
Via: 1.1 google
Alt-Svc: clear

Whois Lookup

Created: 22nd May, 2008
Changed: 15th June, 2020
Expires: 22nd May, 2021
Registrar: Key-Systems GmbH
Status: clientTransferProhibited
Nameservers: ns-1028.awsdns-00.org
ns-1725.awsdns-23.co.uk
ns-674.awsdns-20.net
ns-70.awsdns-08.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: REDACTED FOR PRIVACY
Owner Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: Berlin
Owner Country: DE
Owner Phone: REDACTED FOR PRIVACY
Owner Email: info@domain-contact.org
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
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: info@domain-contact.org
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
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: info@domain-contact.org
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Billing Post Code: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Fax: REDACTED FOR PRIVACY
Billing Email: info@domain-contact.org
Full Whois: Domain Name: zalando.com
Registry Domain ID: 1477954543_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.rrpproxy.net
Registrar URL: http://www.brandshelter.com
Updated Date: 2020-06-15T11:31:44Z
Creation Date: 2008-05-22T18:35:35Z
Registrar Registration Expiration Date: 2021-05-22T18:35:35Z
Registrar: Key-Systems GmbH
Registrar IANA ID: 269
Registrar Abuse Contact Email: abusereport@key-systems.net
Registrar Abuse Contact Phone: +49.68949396850
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Berlin
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: DE
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: info@domain-contact.org
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
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: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: info@domain-contact.org
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
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: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: info@domain-contact.org
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State/Province: REDACTED FOR PRIVACY
Billing Postal Code: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Phone Ext: REDACTED FOR PRIVACY
Billing Fax: REDACTED FOR PRIVACY
Billing Fax Ext: REDACTED FOR PRIVACY
Billing Email: info@domain-contact.org
Name Server: ns-1028.awsdns-00.org
Name Server: ns-1725.awsdns-23.co.uk
Name Server: ns-674.awsdns-20.net
Name Server: ns-70.awsdns-08.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: https://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-04-01T09:22:05Z <<<

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

To contact the registered registrant please proceed to:
https://www.domain-contact.org

Please register your domains at; http://www.brandshelter.com
This data is provided by BrandShelter - Protecting brands with domain expertise around the world!
for information purposes, and to assist persons obtaining information
about or related to domain name registration records.
BrandShelter - Protecting brands with domain expertise around the world! does not guarantee its accuracy.
By submitting a WHOIS query, you agree that you will use this data
only for lawful purposes and that, under no circumstances, you will
use this data to
1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via E-mail
(spam) or
2) enable high volume, automated, electronic processes that apply
to this WHOIS server.
These terms may be changed without prior notice.
By submitting this query, you agree to abide by this policy.
View Raw Whois

Nameservers

Name IP Address
ns-1028.awsdns-00.org 205.251.196.4
ns-1725.awsdns-23.co.uk 205.251.198.189
ns-674.awsdns-20.net 205.251.194.162
ns-70.awsdns-08.com 205.251.192.70
Related

Subdomains

Domain Subdomain
jobs.zalando.com
jobs

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
zalando.de
$4,910,972 USD 4/5
zalando.net
$7,442 USD 3/5
zalando.nl
$172,798 USD 4/5
zalando.org
$788 USD 1/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
zalando-lounge.de
$169,859 USD 3/5
zalando-prive.fr
$15,208 USD 3/5
zalando.co.uk
$313,575 USD 4/5
zalando.net
$7,442 USD 3/5
Love W3 Snoop?
Update Now

zalando.com Infographic

zalando.com by the numbers infographic

Recently Updated

oglasni-portal.com
mobilefokus.com
jwpsrv.com
kant.co.th
taoanhpro.com
trendgrnd.com
mydesi.net
liveatpc.com
stabilitynote.com
vidoevo.com

Recently Viewed

vbaf.com
wwbinhinsi.com
wwbinhindi.com
dkpstudio.com
vstartek.com
josepika.com
gezondenzo.net
matamsa.org
romaselectroengineering.com
dskjewelry.com