Tools & Wizards About Us
tolus.pl screenshot

Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

tolus.pl

TOLUS

Page Load Speed

2.5 sec in total

First Response

420 ms

Resources Loaded

1.4 sec

Page Rendered

639 ms

tolus.pl screenshot

About Website

Click here to check amazing TOLUS content. Otherwise, check out these important facts you probably never knew about tolus.pl

Tolus - tworzymy strony internetowe Olsztyn z użyciem technik HTML, Flash, PHP, Mysql. Sklepy internetowe, katalogi, strony www Olsztyn.

Visit tolus.pl

Key Findings

We analyzed Tolus.pl page load time and found that the first response time was 420 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

tolus.pl performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/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

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

tolus.pl

420 ms

global.css

10 ms

slimbox.css

14 ms

validationengine.css

13 ms

jquery.js

150 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 95% of them (35 requests) were addressed to the original Tolus.pl, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (559 ms) belongs to the original domain Tolus.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 54.8 kB (5%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tolus.pl main page is 1.2 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 6.4 kB

  • Original 8.5 kB
  • After minification 8.3 kB
  • After compression 2.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 6.4 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 39.8 kB

  • Original 1.1 MB
  • After minification 1.1 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. TOLUS images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 8.2 kB

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

CSS Optimization

-12%

Potential reduce by 435 B

  • Original 3.7 kB
  • After minification 3.7 kB
  • After compression 3.2 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. Tolus.pl needs all CSS files to be minified and compressed as it can save up to 435 B or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (21%)

Requests Now

34

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tolus.pl

tolus.pl

420 ms

global.css

global.css

10 ms

slimbox.css

slimbox.css

14 ms

validationengine.css

validationengine.css

13 ms

jquery.js

jquery.js

150 ms

jquery-ui.js

jquery-ui.js

121 ms

fitvids.js

fitvids.js

119 ms

validationengine-pl.js

validationengine-pl.js

438 ms

validationengine.js

validationengine.js

440 ms

slimbox.js

slimbox.js

442 ms

scripts.js

scripts.js

225 ms

bg.jpg

bg.jpg

297 ms

logo.png

logo.png

297 ms

plus.png

plus.png

92 ms

gs_pl_124101120716lubau1.jpg

gs_pl_124101120716lubau1.jpg

298 ms

pl_124101120716lubau1.jpg

pl_124101120716lubau1.jpg

299 ms

gs_pl_014736120716styro1.jpg

gs_pl_014736120716styro1.jpg

298 ms

pl_014736120716styro1.jpg

pl_014736120716styro1.jpg

435 ms

gs_pl_015013120716joico1.jpg

gs_pl_015013120716joico1.jpg

319 ms

pl_015013120716joico1.jpg

pl_015013120716joico1.jpg

316 ms

gs_pl_120936120716junctiox1.jpg

gs_pl_120936120716junctiox1.jpg

318 ms

pl_120936120716junctiox1.jpg

pl_120936120716junctiox1.jpg

317 ms

gs_pl_010853120716totaleko1.jpg

gs_pl_010853120716totaleko1.jpg

296 ms

pl_010853120716totaleko1.jpg

pl_010853120716totaleko1.jpg

312 ms

gs_pl_015236120716happy1.jpg

gs_pl_015236120716happy1.jpg

346 ms

pl_015236120716happy1.jpg

pl_015236120716happy1.jpg

311 ms

gs_pl_124320120716meridian1.jpg

gs_pl_124320120716meridian1.jpg

346 ms

pl_124320120716meridian1.jpg

pl_124320120716meridian1.jpg

346 ms

gs_pl_120317120716cureplex1.jpg

gs_pl_120317120716cureplex1.jpg

348 ms

pl_120317120716cureplex1.jpg

pl_120317120716cureplex1.jpg

349 ms

gs_pl_0121471610131.jpg

gs_pl_0121471610131.jpg

347 ms

pl_0121471610131.jpg

pl_0121471610131.jpg

559 ms

gs_pl_014051120716flight1.jpg

gs_pl_014051120716flight1.jpg

450 ms

pl_014051120716flight1.jpg

pl_014051120716flight1.jpg

464 ms

ga.js

ga.js

26 ms

swiss_721_condensed_bt.woff

swiss_721_condensed_bt.woff

359 ms

__utm.gif

__utm.gif

63 ms

Accessibility Review

tolus.pl accessibility score

60

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

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

tolus.pl 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

SEO Factors

tolus.pl SEO score

92

Search Engine Optimization Advices

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tolus.pl 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Tolus.pl 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

tolus.pl

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