Tools & Wizards About Us
tomaszlyson.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

tomaszlyson.com

Lyson Beekeeping - Your bees are our passion

Page Load Speed

4.7 sec in total

First Response

347 ms

Resources Loaded

3.5 sec

Page Rendered

838 ms

tomaszlyson.com screenshot

About Website

Welcome to tomaszlyson.com homepage info - get ready to check Tomasz Lyson best content right away, or after learning these important things about tomaszlyson.com

Sklep na oprogramowaniu PrestaShop

Visit tomaszlyson.com

Key Findings

We analyzed Tomaszlyson.com page load time and found that the first response time was 347 ms and then it took 4.4 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

tomaszlyson.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

tomaszlyson.com

347 ms

574 ms

theme.css

336 ms

productcomments.css

329 ms

front.css

330 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tomaszlyson.com, 93% (64 requests) were made to Lyson.eu and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (966 ms) relates to the external source Lyson.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 246.2 kB (17%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tomaszlyson.com main page is 1.4 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. 55% of websites need less resources to load. Images take 837.0 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 97.2 kB

  • Original 113.1 kB
  • After minification 90.7 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 22.5 kB, which is 20% 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 97.2 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 73.0 kB

  • Original 837.0 kB
  • After minification 764.0 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. Tomasz Lyson images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.5 kB

  • Original 299.5 kB
  • After minification 298.1 kB
  • After compression 294.0 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

-43%

Potential reduce by 70.6 kB

  • Original 163.8 kB
  • After minification 149.6 kB
  • After compression 93.3 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. Tomaszlyson.com needs all CSS files to be minified and compressed as it can save up to 70.6 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (71%)

Requests Now

63

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tomaszlyson.com

tomaszlyson.com

347 ms

574 ms

theme.css

theme.css

336 ms

productcomments.css

productcomments.css

329 ms

front.css

front.css

330 ms

rs6.css

rs6.css

332 ms

jquery.fancybox.css

jquery.fancybox.css

330 ms

front.css

front.css

331 ms

ph_simpleblog-17.css

ph_simpleblog-17.css

438 ms

custom.css

custom.css

439 ms

front.css

front.css

439 ms

front.css

front.css

440 ms

frontend.min.css

frontend.min.css

441 ms

front.css

front.css

442 ms

front.css

front.css

546 ms

front.css

front.css

546 ms

custom_s_1.css

custom_s_1.css

547 ms

front.css

front.css

549 ms

custom_s_1.css

custom_s_1.css

549 ms

iqitmegamenu_s_1.css

iqitmegamenu_s_1.css

550 ms

font-awesome.css

font-awesome.css

656 ms

custom.css

custom.css

654 ms

font-awesome-preload.css

font-awesome-preload.css

657 ms

js

js

73 ms

core.js

core.js

778 ms

theme.js

theme.js

681 ms

ps_emailsubscription.js

ps_emailsubscription.js

624 ms

conversion-api.js

conversion-api.js

679 ms

jquery.rating.plugin.js

jquery.rating.plugin.js

680 ms

productListingComments.js

productListingComments.js

680 ms

front.js

front.js

681 ms

jquery.fitvids.js

jquery.fitvids.js

769 ms

jquery.fancybox.js

jquery.fancybox.js

769 ms

front.js

front.js

771 ms

ph_simpleblog-17.js

ph_simpleblog-17.js

772 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

786 ms

front.js

front.js

879 ms

instagramLite.min.js

instagramLite.min.js

880 ms

jquery-numerator.min.js

jquery-numerator.min.js

880 ms

lottie-player.js

lottie-player.js

661 ms

frontend.js

frontend.js

666 ms

front.js

front.js

667 ms

front.js

front.js

766 ms

custom_s_1.js

custom_s_1.js

764 ms

front.js

front.js

752 ms

custom.js

custom.js

661 ms

rbtools.min.js

rbtools.min.js

671 ms

rs6.min.js

rs6.min.js

783 ms

logo-1700224457.jpg

logo-1700224457.jpg

527 ms

honey_extractors.png

honey_extractors.png

527 ms

styrofoam_hives.png

styrofoam_hives.png

528 ms

beekeeping_clothing.png

beekeeping_clothing.png

529 ms

beekeeping_assortment.png

beekeeping_assortment.png

542 ms

uncapping.png

uncapping.png

635 ms

silicone_moulds.png

silicone_moulds.png

635 ms

19-thumb.png

19-thumb.png

964 ms

18-thumb.png

18-thumb.png

857 ms

17-thumb.png

17-thumb.png

870 ms

15-thumb.png

15-thumb.png

762 ms

strategia_520.jpg

strategia_520.jpg

695 ms

produkty_520.jpg

produkty_520.jpg

801 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

966 ms

zaangazowanie_520.jpg

zaangazowanie_520.jpg

766 ms

pobierz.png

pobierz.png

856 ms

bottom.jpg

bottom.jpg

860 ms

revicons.woff

revicons.woff

872 ms

css

css

39 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e4.woff

19 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e4.woff

29 ms

Accessibility Review

tomaszlyson.com accessibility score

78

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tomaszlyson.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

High

Page has valid source maps

SEO Factors

tomaszlyson.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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 Tomaszlyson.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 Tomaszlyson.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

tomaszlyson.com

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