Tools & Wizards About Us
hagenburger.com screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

hagenburger.com

Concepts, Design, Frontends & Ruby on Rails ··· Nico Hagenburger

Page Load Speed

3 sec in total

First Response

320 ms

Resources Loaded

2.5 sec

Page Rendered

199 ms

hagenburger.com screenshot

About Website

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

I’m Nico Hagenburger. I’m doing websites with Ruby on Rails, HTML5, Haml, Sass/SCSS & CSS3. And you should click me.

Visit hagenburger.com

Key Findings

We analyzed Hagenburger.com page load time and found that the first response time was 320 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

hagenburger.com performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value3.7 s

86/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

hagenburger.com

320 ms

hagenburger.com

448 ms

www.hagenburger.net

458 ms

hagenburger.css

113 ms

background.png

102 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 10% of them (2 requests) were addressed to the original Hagenburger.com, 90% (18 requests) were made to Hagenburger.net. The less responsive or slowest element that took the longest time to load (947 ms) relates to the external source Hagenburger.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.5 kB (33%)

Content Size

182.2 kB

After Optimization

122.7 kB

  • HTML
  • Images

In fact, the total size of Hagenburger.com main page is 182.2 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. 20% of websites need less resources to load. Images take 171.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 8.3 kB

  • Original 10.5 kB
  • After minification 8.0 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 2.5 kB, which is 24% 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 8.3 kB or 79% of the original size.

Image Optimization

-30%

Potential reduce by 51.2 kB

  • Original 171.7 kB
  • After minification 120.5 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. Obviously, Hagenburger needs image optimization as it can save up to 51.2 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

  • Images
  • CSS

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

Network Requests Diagram

hagenburger.com

hagenburger.com

320 ms

hagenburger.com

hagenburger.com

448 ms

www.hagenburger.net

www.hagenburger.net

458 ms

hagenburger.css

hagenburger.css

113 ms

background.png

background.png

102 ms

header.png

header.png

204 ms

nico-hagenburger-ruby-on-rails-2x.png

nico-hagenburger-ruby-on-rails-2x.png

491 ms

homepage.jpg

homepage.jpg

394 ms

a-vision-for-style-guides-in-2015.png

a-vision-for-style-guides-in-2015.png

299 ms

why-you-might-immediately-fall-in-love-with-sketch.png

why-you-might-immediately-fall-in-love-with-sketch.png

305 ms

style-guide-driven-development.jpg

style-guide-driven-development.jpg

304 ms

javascript-beer-in-bottles.jpg

javascript-beer-in-bottles.jpg

302 ms

create-your-own-gem.jpg

create-your-own-gem.jpg

419 ms

rails-3-1.jpg

rails-3-1.jpg

416 ms

3-ways-to-create-css-sprites-in-rails.jpg

3-ways-to-create-css-sprites-in-rails.jpg

413 ms

better-faster-frontends.jpg

better-faster-frontends.jpg

423 ms

big-frontends-made-simple.jpg

big-frontends-made-simple.jpg

494 ms

FiraGO-Book.woff

FiraGO-Book.woff

945 ms

FiraGO-Bold.woff

FiraGO-Bold.woff

945 ms

FiraGO-Light.woff

FiraGO-Light.woff

947 ms

Accessibility Review

hagenburger.com accessibility score

100

Accessibility Issues

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

hagenburger.com SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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 Hagenburger.com 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 Hagenburger.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

hagenburger.com

Open Graph description is not detected on the main page of Hagenburger. 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: