Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

jbc.be

JBC België - Kinderkleding, dameskleding en herenkleding online

Page Load Speed

2.9 sec in total

First Response

342 ms

Resources Loaded

1.9 sec

Page Rendered

578 ms

jbc.be screenshot

About Website

Click here to check amazing JBC content for Belgium. Otherwise, check out these important facts you probably never knew about jbc.be

Kinderkleding, mode en accessoires voor dames en heren. Shop online bij JBC! Gratis verzending naar je winkel. Gratis retour.

Visit jbc.be

Key Findings

We analyzed Jbc.be page load time and found that the first response time was 342 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

jbc.be performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value3,260 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.507

16/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

jbc.be

342 ms

www.jbc.be

722 ms

068f7863e3.js

121 ms

fonts.css

34 ms

global.css

39 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 65% of them (26 requests) were addressed to the original Jbc.be, 13% (5 requests) were made to Webmedia.jbc.be and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (722 ms) belongs to the original domain Jbc.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 875.5 kB (41%)

Content Size

2.1 MB

After Optimization

1.3 MB

In fact, the total size of Jbc.be main page is 2.1 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. 65% of websites need less resources to load. HTML takes 749.8 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 693.0 kB

  • Original 749.8 kB
  • After minification 744.7 kB
  • After compression 56.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 693.0 kB or 92% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 560.8 kB
  • After minification 560.8 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. JBC images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 182.3 kB

  • Original 660.2 kB
  • After minification 660.2 kB
  • After compression 477.9 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 182.3 kB or 28% of the original size.

CSS Optimization

-0%

Potential reduce by 159 B

  • Original 161.9 kB
  • After minification 161.9 kB
  • After compression 161.8 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. Jbc.be has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (44%)

Requests Now

36

After Optimization

20

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

Accessibility Review

jbc.be accessibility score

73

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

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

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

Image elements do not have [alt] attributes

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.

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

jbc.be 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

jbc.be 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

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jbc.be 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 Jbc.be 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

Open Graph data is detected on the main page of JBC. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: