Tools & Wizards About Us
nelly.de screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

nelly.de

Women’s fashion & designer clothes online - Nelly.com

Page Load Speed

7.8 sec in total

First Response

470 ms

Resources Loaded

6.1 sec

Page Rendered

1.2 sec

nelly.de screenshot

About Website

Visit nelly.de now to see the best up-to-date Nelly content for Germany and also check out these interesting facts you probably never knew about nelly.de

Nelly.com offers clothes for women and girls such as clothing, shoes, dresses, lingerie and trousers from leading brands. At Nelly.com you find the latest fashion online.

Visit nelly.de

Key Findings

We analyzed Nelly.de page load time and found that the first response time was 470 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

nelly.de performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value7,820 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value26.3 s

0/100

10%

Network Requests Diagram

nelly.de

470 ms

719 ms

sitegainer_5619611.js

338 ms

css

319 ms

main.min.css

144 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 21% of them (15 requests) were addressed to the original Nelly.de, 18% (13 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Connect.mecenat.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 395.1 kB (30%)

Content Size

1.3 MB

After Optimization

913.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nelly.de main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 507.3 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 126.2 kB

  • Original 174.0 kB
  • After minification 174.0 kB
  • After compression 47.8 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 126.2 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 507.3 kB
  • After minification 507.3 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Nelly images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 165.7 kB

  • Original 299.3 kB
  • After minification 299.1 kB
  • After compression 133.5 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 165.7 kB or 55% of the original size.

CSS Optimization

-31%

Potential reduce by 103.2 kB

  • Original 328.2 kB
  • After minification 328.2 kB
  • After compression 225.0 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Nelly.de needs all CSS files to be minified and compressed as it can save up to 103.2 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (65%)

Requests Now

51

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nelly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

nelly.de

nelly.de

470 ms

719 ms

sitegainer_5619611.js

sitegainer_5619611.js

338 ms

css

css

319 ms

main.min.css

main.min.css

144 ms

p13n.js

p13n.js

454 ms

scriptsv2.min.js

scriptsv2.min.js

332 ms

index.js

index.js

346 ms

rocket-loader.min.js

rocket-loader.min.js

190 ms

NELLY_2022_COVER_MB_v39_EU_01

NELLY_2022_COVER_MB_v39_EU_01

300 ms

flag-sprite@2x

flag-sprite@2x

285 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

162 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

276 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

274 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

294 ms

HKGrotesk-SemiBold.woff

HKGrotesk-SemiBold.woff

414 ms

HKGrotesk-Bold.woff

HKGrotesk-Bold.woff

724 ms

HKGrotesk-ExtraBold.woff

HKGrotesk-ExtraBold.woff

688 ms

HKGrotesk-Medium.woff

HKGrotesk-Medium.woff

464 ms

HKGrotesk-Regular.woff

HKGrotesk-Regular.woff

535 ms

HKGrotesk-Light.woff

HKGrotesk-Light.woff

650 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

335 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

281 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

335 ms

hotjar-63663.js

hotjar-63663.js

306 ms

gtm.js

gtm.js

307 ms

uc.js

uc.js

228 ms

picturefill.min.js

picturefill.min.js

758 ms

gpt.js

gpt.js

291 ms

scriptsv2.min.js

scriptsv2.min.js

112 ms

p13n_generated.js

p13n_generated.js

419 ms

index.js

index.js

300 ms

cc.js

cc.js

286 ms

bc-v4.min.html

bc-v4.min.html

466 ms

modules.2be88a2123e5e486752f.js

modules.2be88a2123e5e486752f.js

800 ms

pubads_impl_2022092001.js

pubads_impl_2022092001.js

295 ms

ppub_config

ppub_config

400 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

954 ms

events.js

events.js

926 ms

o1ro3vaz.js

o1ro3vaz.js

1763 ms

conversion_async.js

conversion_async.js

973 ms

fbevents.js

fbevents.js

1132 ms

scevent.min.js

scevent.min.js

1110 ms

da07fedd7d9aa.js

da07fedd7d9aa.js

1451 ms

utag.js

utag.js

1722 ms

js

js

483 ms

MecenatConnect.js

MecenatConnect.js

1849 ms

analytics.js

analytics.js

980 ms

NELLY_2022_COVER_DT_v39_EU_02

NELLY_2022_COVER_DT_v39_EU_02

855 ms

1186 ms

1383 ms

css2

css2

285 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf

622 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf

621 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf

622 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0ow.ttf

621 ms

identity.js

identity.js

734 ms

614505702013204

614505702013204

946 ms

collect

collect

648 ms

collect

collect

920 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

407 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

404 ms

utag.2.js

utag.2.js

319 ms

491 ms

undefined;sz=1x2;ord=25040095207

undefined;sz=1x2;ord=25040095207

421 ms

ga-audiences

ga-audiences

317 ms

activityi;src=5116445;type=onsite;cat=landi0;ord=1;num=2472080017230;gtm=2wg9q0;auiddc=1741319619.1664298583;u1=undefined;u2=DE;u3=Nelly;~oref=https%3A%2F%2Fnelly.de%2Fde%2Fwomens-fashion%2F

activityi;src=5116445;type=onsite;cat=landi0;ord=1;num=2472080017230;gtm=2wg9q0;auiddc=1741319619.1664298583;u1=undefined;u2=DE;u3=Nelly;~oref=https%3A%2F%2Fnelly.de%2Fde%2Fwomens-fashion%2F

370 ms

utag.v.js

utag.v.js

72 ms

224 ms

218 ms

o1ro3vaz_1633350655954_es5.js

o1ro3vaz_1633350655954_es5.js

190 ms

src=5116445;type=onsite;cat=landi0;ord=1;num=2472080017230;gtm=2wg9q0;auiddc=*;u1=undefined;u2=DE;u3=Nelly;~oref=https%3A%2F%2Fnelly.de%2Fde%2Fwomens-fashion%2F

src=5116445;type=onsite;cat=landi0;ord=1;num=2472080017230;gtm=2wg9q0;auiddc=*;u1=undefined;u2=DE;u3=Nelly;~oref=https%3A%2F%2Fnelly.de%2Fde%2Fwomens-fashion%2F

47 ms

Accessibility Review

nelly.de accessibility score

72

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

nelly.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

nelly.de SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nelly.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Nelly.de main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

nelly.de

Open Graph description is not detected on the main page of Nelly. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: