Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

tomasp.net

Tomas Petricek - New ways of thinking about programming

Page Load Speed

891 ms in total

First Response

35 ms

Resources Loaded

474 ms

Page Rendered

382 ms

tomasp.net screenshot

About Website

Welcome to tomasp.net homepage info - get ready to check Tomas P best content for Iran right away, or after learning these important things about tomasp.net

I'm an assistant professor at Charles University and a partner at fsharpWorks. I work on making programming simpler and more open. To do so, I combine work on programming systems with history and phil...

Visit tomasp.net

Key Findings

We analyzed Tomasp.net page load time and found that the first response time was 35 ms and then it took 856 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

tomasp.net performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

92/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.165

71/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

tomasp.net

35 ms

tomasp.net

29 ms

css2

43 ms

all.min.css

31 ms

MathJax.js

45 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 52% of them (15 requests) were addressed to the original Tomasp.net, 21% (6 requests) were made to Fonts.gstatic.com and 14% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (351 ms) relates to the external source Tomaspweb.blob.core.windows.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.5 kB (20%)

Content Size

464.8 kB

After Optimization

372.3 kB

In fact, the total size of Tomasp.net main page is 464.8 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. 40% of websites need less resources to load. Images take 399.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 38.4 kB

  • Original 48.1 kB
  • After minification 42.6 kB
  • After compression 9.7 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 5.5 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 38.4 kB or 80% of the original size.

Image Optimization

-14%

Potential reduce by 54.1 kB

  • Original 399.5 kB
  • After minification 345.4 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, Tomas P needs image optimization as it can save up to 54.1 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.

Requests Breakdown

Number of requests can be reduced by 6 (32%)

Requests Now

19

After Optimization

13

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

Accessibility Review

tomasp.net accessibility score

64

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

tomasp.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

tomasp.net SEO score

91

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

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Tomasp.net 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 Tomasp.net 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 Tomas P. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: