Tools & Wizards About Us

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

jumbo.com

Altijd lage prijzen op je dagelijkse boodschappen | Jumbo

Page Load Speed

4.6 sec in total

First Response

1.6 sec

Resources Loaded

2.2 sec

Page Rendered

874 ms

About Website

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

Ontdek het ruime assortiment van Jumbo! ✓ Altijd lage prijzen ✓ Boodschappen thuisbezorgen ✓ Heerlijke recepten ✓ Handige Jumbo app

Visit jumbo.com

Key Findings

We analyzed Jumbo.com page load time and found that the first response time was 1.6 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

jumbo.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value3.6 s

92/100

10%

Network Requests Diagram

www.jumbo.com

1555 ms

otSDKStub.js

32 ms

jwa.modern.min.js

98 ms

jwa.min.js

97 ms

style.wy2c-Y-8.css

105 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 64% of them (21 requests) were addressed to the original Jumbo.com, 12% (4 requests) were made to Static-images.jumbo.com and 9% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Jumbo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 459.7 kB (29%)

Content Size

1.6 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Jumbo.com main page is 1.6 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. Images take 848.2 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 398.4 kB

  • Original 542.8 kB
  • After minification 539.9 kB
  • After compression 144.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. 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 398.4 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 1 B

  • Original 848.2 kB
  • After minification 848.1 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. Jumbo images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 61.3 kB

  • Original 207.1 kB
  • After minification 207.1 kB
  • After compression 145.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 61.3 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (31%)

Requests Now

26

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

jumbo.com accessibility score

90

Accessibility Issues

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

jumbo.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

jumbo.com SEO score

100

Search Engine Optimization Advices

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 Jumbo.com 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 Jumbo.com 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 description is not detected on the main page of Jumbo. 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: