Tools & Wizards About Us
assem.nl screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

assem.nl

Shop de nieuwe collectie voor dames en heren | Assem

Page Load Speed

4.4 sec in total

First Response

377 ms

Resources Loaded

2.1 sec

Page Rendered

1.9 sec

assem.nl screenshot

About Website

Visit assem.nl now to see the best up-to-date Assem content for Netherlands and also check out these interesting facts you probably never knew about assem.nl

✓Voor 23.59u besteld, morgen in huis ✓ Gratis verzending & retourneren binnen 100 dagen* ✓Achteraf betalen mogelijk

Visit assem.nl

Key Findings

We analyzed Assem.nl page load time and found that the first response time was 377 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

assem.nl performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.09

92/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

assem.nl

377 ms

assem.nl

403 ms

www.assem.nl

427 ms

lazysizes-5.2.2.min.js

381 ms

gtm.js

236 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 86% of them (44 requests) were addressed to the original Assem.nl, 8% (4 requests) were made to Googletagmanager.com and 2% (1 request) were made to Cdn.cquotient.com. The less responsive or slowest element that took the longest time to load (540 ms) belongs to the original domain Assem.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 320.3 kB (7%)

Content Size

4.5 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Assem.nl main page is 4.5 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 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 318.4 kB

  • Original 349.8 kB
  • After minification 277.4 kB
  • After compression 31.4 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. This page needs HTML code to be minified as it can gain 72.4 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 318.4 kB or 91% of the original size.

Image Optimization

-0%

Potential reduce by 1.6 kB

  • Original 3.9 MB
  • After minification 3.9 MB

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. Assem images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 233 B

  • Original 210.5 kB
  • After minification 210.5 kB
  • After compression 210.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 114 B

  • Original 84.2 kB
  • After minification 84.2 kB
  • After compression 84.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. Assem.nl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (54%)

Requests Now

37

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

assem.nl

assem.nl

377 ms

assem.nl

assem.nl

403 ms

www.assem.nl

www.assem.nl

427 ms

lazysizes-5.2.2.min.js

lazysizes-5.2.2.min.js

381 ms

gtm.js

gtm.js

236 ms

global.css

global.css

69 ms

header.css

header.css

100 ms

pagedesigner.css

pagedesigner.css

94 ms

main.js

main.js

225 ms

loginPopup.js

loginPopup.js

222 ms

emailPopup.js

emailPopup.js

169 ms

pagedesigner.js

pagedesigner.js

222 ms

pdMeasurement.js

pdMeasurement.js

222 ms

video.js

video.js

540 ms

productslider.js

productslider.js

228 ms

tagmanager.js

tagmanager.js

227 ms

countdownBar.js

countdownBar.js

239 ms

logo.svg

logo.svg

223 ms

caret-down-solid.svg

caret-down-solid.svg

220 ms

Dames_schoenen.jpg

Dames_schoenen.jpg

225 ms

Dames_kleding.jpg

Dames_kleding.jpg

231 ms

Dames_inspiratie.jpg

Dames_inspiratie.jpg

230 ms

Heren_schoenen.jpg

Heren_schoenen.jpg

228 ms

Heren_kleding.jpg

Heren_kleding.jpg

232 ms

dwanalytics-22.2.js

dwanalytics-22.2.js

217 ms

dwac-21.7.js

dwac-21.7.js

219 ms

gretel.min.js

gretel.min.js

29 ms

Assem_Homeimage_desktop_home.jpg

Assem_Homeimage_desktop_home.jpg

219 ms

Instagram.png

Instagram.png

216 ms

Facebook.png

Facebook.png

287 ms

Tiktok.png

Tiktok.png

219 ms

Linkedin.png

Linkedin.png

287 ms

loader-tile.gif

loader-tile.gif

153 ms

Flink-Regular.woff

Flink-Regular.woff

153 ms

Flink-Light.woff

Flink-Light.woff

153 ms

Flink-Bold.woff

Flink-Bold.woff

154 ms

icon-font.ttf

icon-font.ttf

161 ms

Fahkwang-SemiBold.woff

Fahkwang-SemiBold.woff

157 ms

Fahkwang-Bold.woff

Fahkwang-Bold.woff

158 ms

Fahkwang-Regular.woff

Fahkwang-Regular.woff

157 ms

Roboto-Regular.woff

Roboto-Regular.woff

159 ms

Roboto-Light.woff

Roboto-Light.woff

161 ms

Roboto-Medium.woff

Roboto-Medium.woff

162 ms

js

js

113 ms

landing

landing

216 ms

api.ipify.org

api.ipify.org

220 ms

cart.css

cart.css

140 ms

destination

destination

135 ms

js

js

204 ms

checkout.css

checkout.css

95 ms

cat-landing.css

cat-landing.css

90 ms

Accessibility Review

assem.nl accessibility score

74

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

High

[role]s are not contained by their required parent element

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

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

assem.nl best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

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

assem.nl SEO score

86

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 uses legible font sizes

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Assem.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Assem.nl 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

assem.nl

Open Graph description is not detected on the main page of Assem. 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: