Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

jerj.be

JerJ Photography

Page Load Speed

10 sec in total

First Response

3.4 sec

Resources Loaded

5.9 sec

Page Rendered

692 ms

jerj.be screenshot

About Website

Visit jerj.be now to see the best up-to-date JerJ content and also check out these interesting facts you probably never knew about jerj.be

Visit jerj.be

Key Findings

We analyzed Jerj.be page load time and found that the first response time was 3.4 sec and then it took 6.6 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

jerj.be performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value270 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.127

82/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

jerj.be

3374 ms

reset.css

128 ms

style.css

217 ms

galleria.css

214 ms

nggallery.css

231 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that all of those requests were addressed to Jerj.be and no external sources were called. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Jerj.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 276.9 kB (20%)

Content Size

1.4 MB

After Optimization

1.1 MB

In fact, the total size of Jerj.be main page is 1.4 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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 99.1 kB

  • Original 108.7 kB
  • After minification 79.0 kB
  • After compression 9.6 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 29.7 kB, which is 27% 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 99.1 kB or 91% of the original size.

Image Optimization

-4%

Potential reduce by 40.2 kB

  • Original 1.1 MB
  • After minification 1.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. JerJ images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 118.4 kB

  • Original 168.3 kB
  • After minification 148.4 kB
  • After compression 49.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 118.4 kB or 70% of the original size.

CSS Optimization

-79%

Potential reduce by 19.1 kB

  • Original 24.2 kB
  • After minification 17.8 kB
  • After compression 5.1 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. Jerj.be needs all CSS files to be minified and compressed as it can save up to 19.1 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (12%)

Requests Now

98

After Optimization

86

The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JerJ. 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 from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

jerj.be accessibility score

63

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

jerj.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

jerj.be SEO score

79

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jerj.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jerj.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 description is not detected on the main page of JerJ. 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: