Tools & Wizards About Us
sturmg.eu screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

sturmg.eu

Gabor Sturm Web Developer

Page Load Speed

1.2 sec in total

First Response

290 ms

Resources Loaded

788 ms

Page Rendered

151 ms

sturmg.eu screenshot

About Website

Welcome to sturmg.eu homepage info - get ready to check Sturm G best content right away, or after learning these important things about sturmg.eu

gabor sturm senior developer's personal site, showing his portfolio

Visit sturmg.eu

Key Findings

We analyzed Sturmg.eu page load time and found that the first response time was 290 ms and then it took 939 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

sturmg.eu performance score

0

Network Requests Diagram

sturmg.eu

290 ms

html5reset.css

86 ms

col.css

158 ms

12cols.css

161 ms

common.css

158 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 80% of them (8 requests) were addressed to the original Sturmg.eu, 10% (1 request) were made to Fonts.googleapis.com and 10% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (398 ms) belongs to the original domain Sturmg.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.8 kB (52%)

Content Size

149.6 kB

After Optimization

71.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sturmg.eu main page is 149.6 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. Only 5% of websites need less resources to load. Javascripts take 96.1 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 1.3 kB

  • Original 2.3 kB
  • After minification 2.1 kB
  • After compression 959 B

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 1.3 kB or 58% of the original size.

Image Optimization

-19%

Potential reduce by 8.4 kB

  • Original 43.9 kB
  • After minification 35.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, Sturm G needs image optimization as it can save up to 8.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 62.5 kB

  • Original 96.1 kB
  • After minification 96.1 kB
  • After compression 33.6 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 62.5 kB or 65% of the original size.

CSS Optimization

-76%

Potential reduce by 5.6 kB

  • Original 7.3 kB
  • After minification 4.8 kB
  • After compression 1.8 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. Sturmg.eu needs all CSS files to be minified and compressed as it can save up to 5.6 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (50%)

Requests Now

8

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sturmg.eu

sturmg.eu

290 ms

html5reset.css

html5reset.css

86 ms

col.css

col.css

158 ms

12cols.css

12cols.css

161 ms

common.css

common.css

158 ms

css

css

64 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

398 ms

common.js

common.js

166 ms

small_circles.png

small_circles.png

383 ms

LeFlHvsZjXu2c3ZRgBq9nKCWcynf_cDxXwCLxiixG1c.ttf

LeFlHvsZjXu2c3ZRgBq9nKCWcynf_cDxXwCLxiixG1c.ttf

58 ms

SEO Factors

sturmg.eu SEO score

0

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 Sturmg.eu 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 Sturmg.eu 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

sturmg.eu

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