Tools & Wizards About Us
francik.name screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

francik.name

Coming Soon

Page Load Speed

1.1 sec in total

First Response

252 ms

Resources Loaded

741 ms

Page Rendered

138 ms

francik.name screenshot

About Website

Visit francik.name now to see the best up-to-date Francik content and also check out these interesting facts you probably never knew about francik.name

Visit francik.name

Key Findings

We analyzed Francik.name page load time and found that the first response time was 252 ms and then it took 879 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

francik.name performance score

0

Network Requests Diagram

francik.name

252 ms

default.css

133 ms

index2.php

490 ms

jarek.jpg

198 ms

valid-xhtml10-blue

42 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 38% of them (3 requests) were addressed to the original Francik.name, 25% (2 requests) were made to Google-analytics.com and 13% (1 request) were made to Www3.clustrmaps.com. The less responsive or slowest element that took the longest time to load (490 ms) relates to the external source Www3.clustrmaps.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.2 kB (14%)

Content Size

64.6 kB

After Optimization

55.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Francik.name main page is 64.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. Images take 42.7 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 2.9 kB

  • Original 4.0 kB
  • After minification 2.6 kB
  • After compression 1.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 1.4 kB, which is 35% 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 2.9 kB or 72% of the original size.

Image Optimization

-14%

Potential reduce by 5.9 kB

  • Original 42.7 kB
  • After minification 36.8 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, Francik needs image optimization as it can save up to 5.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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.

CSS Optimization

-53%

Potential reduce by 355 B

  • Original 666 B
  • After minification 540 B
  • After compression 311 B

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. Francik.name needs all CSS files to be minified and compressed as it can save up to 355 B or 53% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

francik.name

francik.name

252 ms

default.css

default.css

133 ms

index2.php

index2.php

490 ms

jarek.jpg

jarek.jpg

198 ms

valid-xhtml10-blue

valid-xhtml10-blue

42 ms

vcss-blue

vcss-blue

43 ms

ga.js

ga.js

6 ms

__utm.gif

__utm.gif

11 ms

SEO Factors

francik.name SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Francik.name 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 Francik.name main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

francik.name

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