Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

berghof-handbook.net

Berghof Foundation

Page Load Speed

3.2 sec in total

First Response

482 ms

Resources Loaded

2.5 sec

Page Rendered

219 ms

berghof-handbook.net screenshot

About Website

Welcome to berghof-handbook.net homepage info - get ready to check Berghof Handbook best content right away, or after learning these important things about berghof-handbook.net

A non-governmental organisation supporting people in conflict in their efforts to achieve sustainable peace through conflict transformation and peacebuilding

Visit berghof-handbook.net

Key Findings

We analyzed Berghof-handbook.net page load time and found that the first response time was 482 ms and then it took 2.7 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

berghof-handbook.net performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.218

57/100

15%

TTI (Time to Interactive)

Value20.5 s

2/100

10%

Network Requests Diagram

482 ms

stylesheet_05321f0a32.css

306 ms

bootstrap.css

648 ms

jquery.fancybox.css

432 ms

fonts.css

210 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Berghof-handbook.net, 19% (5 requests) were made to Berghof-foundation.org and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (856 ms) relates to the external source Script.berghof-foundation.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.4 kB (64%)

Content Size

397.1 kB

After Optimization

142.7 kB

In fact, the total size of Berghof-handbook.net main page is 397.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 194.1 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 15.5 kB

  • Original 20.2 kB
  • After minification 19.8 kB
  • After compression 4.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 15.5 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 466 B

  • Original 38.3 kB
  • After minification 37.9 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. Berghof Handbook images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 117.1 kB

  • Original 194.1 kB
  • After minification 185.3 kB
  • After compression 77.0 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 117.1 kB or 60% of the original size.

CSS Optimization

-84%

Potential reduce by 121.3 kB

  • Original 144.4 kB
  • After minification 115.2 kB
  • After compression 23.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. Berghof-handbook.net needs all CSS files to be minified and compressed as it can save up to 121.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (60%)

Requests Now

25

After Optimization

10

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

Accessibility Review

berghof-handbook.net accessibility score

70

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

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

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

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

berghof-handbook.net 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

SEO Factors

berghof-handbook.net SEO score

86

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

    EN

  • Encoding

    UTF-8

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