Tools & Wizards About Us
tomlechner.com screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    88% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

tomlechner.com

Tom Lechner's Art

Page Load Speed

2.7 sec in total

First Response

13 ms

Resources Loaded

2.3 sec

Page Rendered

404 ms

tomlechner.com screenshot

About Website

Click here to check amazing Tom Lechner content. Otherwise, check out these important facts you probably never knew about tomlechner.com

See here Tom Lechner's cartoons, photography, sculptures, and prints.

Visit tomlechner.com

Key Findings

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

tomlechner.com performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

tomlechner.com

13 ms

www.tomlechner.com

1492 ms

style.css

9 ms

css

32 ms

style.min.css

12 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 49% of them (18 requests) were addressed to the original Tomlechner.com, 16% (6 requests) were made to Youtube.com and 11% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Tomlechner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 274.7 kB (11%)

Content Size

2.5 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tomlechner.com main page is 2.5 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.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 31.1 kB

  • Original 40.0 kB
  • After minification 36.7 kB
  • After compression 8.9 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 31.1 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 20.8 kB

  • Original 2.0 MB
  • After minification 2.0 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. Tom Lechner images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 221.6 kB

  • Original 390.6 kB
  • After minification 390.6 kB
  • After compression 169.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 221.6 kB or 57% of the original size.

CSS Optimization

-2%

Potential reduce by 1.2 kB

  • Original 75.2 kB
  • After minification 75.2 kB
  • After compression 74.0 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. Tomlechner.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (33%)

Requests Now

30

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tomlechner.com

tomlechner.com

13 ms

www.tomlechner.com

www.tomlechner.com

1492 ms

style.css

style.css

9 ms

css

css

32 ms

style.min.css

style.min.css

12 ms

classic-themes.min.css

classic-themes.min.css

9 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

10 ms

pika-floatingrock.png

pika-floatingrock.png

55 ms

392554869

392554869

489 ms

sR0S4hzExVE

sR0S4hzExVE

104 ms

GPz3BniLSFw

GPz3BniLSFw

428 ms

titleimage3.png

titleimage3.png

14 ms

youtube.png

youtube.png

11 ms

mastodon-64x64.png

mastodon-64x64.png

10 ms

vimeo.png

vimeo.png

13 ms

flickr.png

flickr.png

13 ms

spacer.gif

spacer.gif

13 ms

stripe.gif

stripe.gif

16 ms

tortoiseharebike-m-300x196.jpg

tortoiseharebike-m-300x196.jpg

18 ms

scale_logo_lg-300x141.png

scale_logo_lg-300x141.png

18 ms

LaidoutBanner-300x150.png

LaidoutBanner-300x150.png

22 ms

lgm-2018-drawing-277x300.jpg

lgm-2018-drawing-277x300.jpg

20 ms

p01-271x300.jpg

p01-271x300.jpg

20 ms

www-player.css

www-player.css

13 ms

www-embed-player.js

www-embed-player.js

26 ms

base.js

base.js

47 ms

ad_status.js

ad_status.js

236 ms

L24uOtqvNfFRO5TOxiIOVgM50wph5QKjT82e9pNVgC0.js

L24uOtqvNfFRO5TOxiIOVgM50wph5QKjT82e9pNVgC0.js

187 ms

embed.js

embed.js

119 ms

B50NF7ZDq37KMUvlO015jKJu.ttf

B50NF7ZDq37KMUvlO015jKJu.ttf

100 ms

0ybgGDoxxrvAnPhYGzMlQLzuMasz6Df2MHGeHmmZ.ttf

0ybgGDoxxrvAnPhYGzMlQLzuMasz6Df2MHGeHmmZ.ttf

109 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

52 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

53 ms

id

id

35 ms

Create

Create

97 ms

Create

Create

99 ms

api.js

api.js

78 ms

Accessibility Review

tomlechner.com accessibility score

92

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

tomlechner.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tomlechner.com SEO score

88

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

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tomlechner.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 Tomlechner.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

tomlechner.com

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