Tools & Wizards About Us
1-thomas.ru screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

1-thomas.ru

1-thomas - Запчасти и аксессуары Thomas | Сервисный центр Thomas

Page Load Speed

2.8 sec in total

First Response

260 ms

Resources Loaded

2.3 sec

Page Rendered

251 ms

1-thomas.ru screenshot

About Website

Welcome to 1-thomas.ru homepage info - get ready to check 1 Thomas best content for Russia right away, or after learning these important things about 1-thomas.ru

Запчасти для пылесоса Thomas, в наличии и под заказ от официального производителя, интернет магазин запчастей для пылесоса томас

Visit 1-thomas.ru

Key Findings

We analyzed 1-thomas.ru page load time and found that the first response time was 260 ms and then it took 2.6 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

1-thomas.ru performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value9,480 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

1-thomas.ru

260 ms

niftycube.js

107 ms

overridestyles.css

176 ms

head.js

241 ms

main.css

237 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 89% of them (33 requests) were addressed to the original 1-thomas.ru, 5% (2 requests) were made to Counter.yadro.ru and 3% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (821 ms) belongs to the original domain 1-thomas.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 90.8 kB (29%)

Content Size

316.7 kB

After Optimization

226.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1-thomas.ru main page is 316.7 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. 20% of websites need less resources to load. Images take 209.4 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 14.3 kB

  • Original 19.8 kB
  • After minification 18.9 kB
  • After compression 5.4 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 14.3 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 6.5 kB

  • Original 209.4 kB
  • After minification 202.9 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. 1 Thomas images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 46.3 kB

  • Original 58.8 kB
  • After minification 42.7 kB
  • After compression 12.5 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 46.3 kB or 79% of the original size.

CSS Optimization

-82%

Potential reduce by 23.5 kB

  • Original 28.7 kB
  • After minification 22.9 kB
  • After compression 5.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. 1-thomas.ru needs all CSS files to be minified and compressed as it can save up to 23.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (41%)

Requests Now

34

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1-thomas.ru

1-thomas.ru

260 ms

niftycube.js

niftycube.js

107 ms

overridestyles.css

overridestyles.css

176 ms

head.js

head.js

241 ms

main.css

main.css

237 ms

general.css

general.css

269 ms

functions.js

functions.js

821 ms

behavior.js

behavior.js

704 ms

widget_checkout.js

widget_checkout.js

323 ms

frame.js

frame.js

416 ms

thomas.jpg

thomas.jpg

333 ms

line1.jpg

line1.jpg

106 ms

glr_arrow_category_small_white.gif

glr_arrow_category_small_white.gif

104 ms

line2.jpg

line2.jpg

176 ms

line3.jpg

line3.jpg

165 ms

rss-feed.png

rss-feed.png

187 ms

spares-1ms.jpg

spares-1ms.jpg

278 ms

brush-nozzle-223.jpg

brush-nozzle-223.jpg

232 ms

hose-1n0.jpg

hose-1n0.jpg

221 ms

tube-1sn.jpg

tube-1sn.jpg

241 ms

filter-bags-1c6.jpg

filter-bags-1c6.jpg

229 ms

protex-16p.jpg

protex-16p.jpg

285 ms

supply-line-filter-11cv.jpg

supply-line-filter-11cv.jpg

286 ms

polosa-nizz.jpg

polosa-nizz.jpg

304 ms

787237-thomas_thm.jpg

787237-thomas_thm.jpg

316 ms

787515_thm.jpg

787515_thm.jpg

348 ms

profloor_thm.jpg

profloor_thm.jpg

362 ms

call-centre-1.jpg

call-centre-1.jpg

429 ms

knopki-1.jpg

knopki-1.jpg

414 ms

servis-tomas.jpg

servis-tomas.jpg

476 ms

repair.jpg

repair.jpg

428 ms

q-protek.jpg

q-protek.jpg

439 ms

hit

hit

326 ms

watch.js

watch.js

1 ms

hit

hit

160 ms

counter

counter

393 ms

niftyCorners.css

niftyCorners.css

59 ms

Accessibility Review

1-thomas.ru accessibility score

94

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

[id] attributes on active, focusable elements are not unique

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

1-thomas.ru 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

1-thomas.ru SEO score

93

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

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1-thomas.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 1-thomas.ru 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

1-thomas.ru

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