Report Summary

  • 0

    Performance

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fhollenbach.org

Florian M. Hollenbach’s Website - Florian M. Hollenbach

Page Load Speed

379 ms in total

First Response

39 ms

Resources Loaded

256 ms

Page Rendered

84 ms

fhollenbach.org screenshot

About Website

Visit fhollenbach.org now to see the best up-to-date F Hollenbach content and also check out these interesting facts you probably never knew about fhollenbach.org

Website for Florian M. Hollenbach, Associate Professor, Department of International Economics, Government, and Business, Copenhagen Business School

Visit fhollenbach.org

Key Findings

We analyzed Fhollenbach.org page load time and found that the first response time was 39 ms and then it took 340 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

fhollenbach.org performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

fhollenbach.org

39 ms

fhollenbach.org

41 ms

main.css

21 ms

IMG_6036.jpeg

35 ms

main.min.js

39 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 71% of them (5 requests) were addressed to the original Fhollenbach.org, 14% (1 request) were made to Use.fontawesome.com and 14% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (67 ms) relates to the external source Use.fontawesome.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 15.2 kB (3%)

Content Size

545.3 kB

After Optimization

530.1 kB

In fact, the total size of Fhollenbach.org main page is 545.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 359.1 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 15.1 kB

  • Original 22.2 kB
  • After minification 19.9 kB
  • After compression 7.1 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 2.4 kB, which is 11% 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 15.1 kB or 68% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 164.0 kB
  • After minification 164.0 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. F Hollenbach images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 359.1 kB
  • After minification 359.1 kB
  • After compression 359.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. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of F Hollenbach. According to our analytics all requests are already optimized.

Accessibility Review

fhollenbach.org accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

fhollenbach.org 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

SEO Factors

fhollenbach.org SEO score

93

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

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 Fhollenbach.org 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 Fhollenbach.org 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 F Hollenbach. 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: