Access honneloeloe.nl. Home

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value190 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

honneloeloe.nl

401 ms

www.honneloeloe.nl

446 ms

app.css

690 ms

css

117 ms

font-awesome.min.css

82 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 57% of them (39 requests) were addressed to the original Honneloeloe.nl, 25% (17 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Honneloeloe.nl.

Content Size

9.0 MB

After Optimization

7.1 MB

In fact, the total size of Honneloeloe.nl main page is 9.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 103.2 kB

Original 117.4 kB
After minification 96.4 kB
After compression 14.2 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 21.0 kB, which is 18% 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 103.2 kB or 88% of the original size.

Image Optimization

-16%

Potential reduce by 1.3 MB

Original 8.3 MB
After minification 7.0 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. Obviously, Honneloeloe needs image optimization as it can save up to 1.3 MB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-79%

Potential reduce by 266.5 kB

Original 336.2 kB
After minification 200.3 kB
After compression 69.8 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 266.5 kB or 79% of the original size.

CSS Optimization

-86%

Potential reduce by 251.7 kB

Original 293.4 kB
After minification 245.4 kB
After compression 41.7 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. Honneloeloe.nl needs all CSS files to be minified and compressed as it can save up to 251.7 kB or 86% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

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

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Links do not have a discernible name

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

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

NL
Language Claimed

NL
Encoding

UTF-8

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

honneloeloe.nl

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Home

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

honneloeloe.nl

www.honneloeloe.nl

app.css

css

font-awesome.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

honneloeloe.nl

www.honneloeloe.nl

app.css

css

font-awesome.min.css

jquery.js

bootstrap.js

facebook.js

css

ico-parking.png

ico-my-account.png

logo.png

overzicht.png

voorjaar-2016.png

bruidsmeisjes-volwassen.png

bruid-1.png

zomer2016-1.png

Zomer2016-2.png

vintage-retro.png

bruidsmeisje-04a.png

gala-groot.png

galajurken.png

cocktailjurken.png

trouwjurken.png

grote-maten.png

vintage.png

bruidsmeisjes-volwassen.png

gelegenheden.png

accessoires.png

kleintjes.png

sweet-16.png

moeder-van-de-bruid.png

low-budget.png

Afbeelding8.png

rtl4-klein.png

kom-binnen.png

facebook-logo.png

sdk.js

analytics.js

fbevents.js

ico-clock.png

ico-eggs.png

check-circle.png