Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

jajo.com

JAJO. Closing the circle, together.

Page Load Speed

6.7 sec in total

First Response

291 ms

Resources Loaded

5.8 sec

Page Rendered

591 ms

jajo.com screenshot

About Website

Click here to check amazing JAJO content. Otherwise, check out these important facts you probably never knew about jajo.com

JAJO. Hoofdkantoor in ’s-Hertogenbosch. Wij ontwikkelen, bouwen, onderhouden, herstellen en oogsten. #ClosingTheCircleTogether

Visit jajo.com

Key Findings

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

Performance Metrics

jajo.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

jajo.com

291 ms

jajo.com

387 ms

www.jajo.com

2614 ms

style.css

190 ms

uc.js

37 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 88% of them (46 requests) were addressed to the original Jajo.com, 4% (2 requests) were made to Googletagmanager.com and 2% (1 request) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Jajo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 554.4 kB (51%)

Content Size

1.1 MB

After Optimization

535.8 kB

In fact, the total size of Jajo.com main page is 1.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. 60% of websites need less resources to load. Javascripts take 846.4 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 131.4 kB

  • Original 147.6 kB
  • After minification 140.2 kB
  • After compression 16.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. 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 131.4 kB or 89% of the original size.

JavaScript Optimization

-50%

Potential reduce by 422.5 kB

  • Original 846.4 kB
  • After minification 846.4 kB
  • After compression 423.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 422.5 kB or 50% of the original size.

CSS Optimization

-1%

Potential reduce by 554 B

  • Original 96.2 kB
  • After minification 96.0 kB
  • After compression 95.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. Jajo.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (70%)

Requests Now

46

After Optimization

14

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

Accessibility Review

jajo.com accessibility score

80

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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

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

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

Best Practices

jajo.com best practices score

83

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

Page has valid source maps

SEO Factors

jajo.com SEO score

84

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

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 Jajo.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 Jajo.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 data is detected on the main page of JAJO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: