Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

Page Load Speed

5.7 sec in total

First Response

1 sec

Resources Loaded

4.5 sec

Page Rendered

182 ms

tobiasz.com screenshot

About Website

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

Piotr Tobiasz Kozłowski

Visit tobiasz.com

Key Findings

We analyzed Tobiasz.com page load time and found that the first response time was 1 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

tobiasz.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.802

5/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

tobiasz.com

1019 ms

www.tobiasz.com

1415 ms

wp-emoji-release.min.js

254 ms

wplike2get.min.css

269 ms

third-parties.css

263 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 71% of them (54 requests) were addressed to the original Tobiasz.com, 7% (5 requests) were made to Pixel.wp.com and 4% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Tobiasz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 753.3 kB (21%)

Content Size

3.6 MB

After Optimization

2.8 MB

In fact, the total size of Tobiasz.com main page is 3.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 37.8 kB

  • Original 50.8 kB
  • After minification 49.1 kB
  • After compression 13.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. 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 37.8 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 158.4 kB

  • Original 2.7 MB
  • After minification 2.6 MB

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. Tobiasz images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 370.4 kB

  • Original 556.0 kB
  • After minification 545.3 kB
  • After compression 185.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 370.4 kB or 67% of the original size.

CSS Optimization

-79%

Potential reduce by 186.7 kB

  • Original 235.4 kB
  • After minification 195.1 kB
  • After compression 48.7 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. Tobiasz.com needs all CSS files to be minified and compressed as it can save up to 186.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (54%)

Requests Now

69

After Optimization

32

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

Best Practices

tobiasz.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

tobiasz.com SEO score

50

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

Document doesn't have a <title> element

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

    N/A

  • Language Claimed

    PL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tobiasz.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Polish. Our system also found out that Tobiasz.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

Open Graph data is detected on the main page of Tobiasz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: