Tools & Wizards About Us
thomsonrail.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

thomsonrail.com

Thomson Rail

Page Load Speed

2.9 sec in total

First Response

392 ms

Resources Loaded

1.8 sec

Page Rendered

706 ms

thomsonrail.com screenshot

About Website

Click here to check amazing Thomson Rail content. Otherwise, check out these important facts you probably never knew about thomsonrail.com

The world’s largest range of specialized maintenance equipment for railway applications

Visit thomsonrail.com

Key Findings

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

thomsonrail.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.445

21/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

thomsonrail.com

392 ms

style.min.css

69 ms

style.css

54 ms

mediaelementplayer-legacy.min.css

67 ms

wp-mediaelement.min.css

86 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 69% of them (46 requests) were addressed to the original Thomsonrail.com, 13% (9 requests) were made to Fonts.gstatic.com and 9% (6 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (642 ms) belongs to the original domain Thomsonrail.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.0 kB (2%)

Content Size

5.4 MB

After Optimization

5.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thomsonrail.com main page is 5.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. Only a small number of websites need less resources to load. Images take 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 79.2 kB

  • Original 98.7 kB
  • After minification 96.4 kB
  • After compression 19.6 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 79.2 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.9 MB
  • After minification 4.9 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. Thomson Rail images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 32.4 kB

  • Original 258.4 kB
  • After minification 258.4 kB
  • After compression 225.9 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 32.4 kB or 13% of the original size.

CSS Optimization

-9%

Potential reduce by 18.4 kB

  • Original 211.8 kB
  • After minification 211.8 kB
  • After compression 193.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. Thomsonrail.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 44 (79%)

Requests Now

56

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thomson Rail. 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 21 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

thomsonrail.com

thomsonrail.com

392 ms

style.min.css

style.min.css

69 ms

style.css

style.css

54 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

67 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

86 ms

kk-star-ratings.min.css

kk-star-ratings.min.css

94 ms

settings.css

settings.css

82 ms

style.css

style.css

85 ms

style.min.css

style.min.css

76 ms

latest.css

latest.css

84 ms

font-awesome.min.css

font-awesome.min.css

86 ms

grid-system.css

grid-system.css

88 ms

style.css

style.css

117 ms

element-fancy-box.css

element-fancy-box.css

96 ms

jquery.fancybox.css

jquery.fancybox.css

105 ms

css

css

90 ms

responsive.css

responsive.css

105 ms

skin-material.css

skin-material.css

141 ms

js_composer.min.css

js_composer.min.css

99 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

146 ms

jquery.min.js

jquery.min.js

75 ms

jquery-migrate.min.js

jquery-migrate.min.js

76 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

175 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

174 ms

js

js

173 ms

animate.min.css

animate.min.css

171 ms

css

css

106 ms

coblocks-animation.js

coblocks-animation.js

249 ms

tiny-swiper.js

tiny-swiper.js

329 ms

coblocks-tinyswiper-initializer.js

coblocks-tinyswiper-initializer.js

328 ms

kk-star-ratings.min.js

kk-star-ratings.min.js

327 ms

salient-social.js

salient-social.js

329 ms

jquery.easing.js

jquery.easing.js

328 ms

jquery.mousewheel.js

jquery.mousewheel.js

329 ms

priority.js

priority.js

330 ms

transit.js

transit.js

330 ms

waypoints.js

waypoints.js

328 ms

modernizr.js

modernizr.js

331 ms

imagesLoaded.min.js

imagesLoaded.min.js

328 ms

hoverintent.js

hoverintent.js

330 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

329 ms

superfish.js

superfish.js

331 ms

init.js

init.js

333 ms

touchswipe.min.js

touchswipe.min.js

331 ms

e-202437.js

e-202437.js

80 ms

js_composer_front.min.js

js_composer_front.min.js

331 ms

wiv.js

wiv.js

641 ms

logo.jpg

logo.jpg

90 ms

Home-Page-Banner.jpg

Home-Page-Banner.jpg

93 ms

Komatsu-Pw150-Tandem-Lifting-022.jpg

Komatsu-Pw150-Tandem-Lifting-022.jpg

91 ms

20190115_120740.mp4.00_00_56_10.Still001-Copy.jpg

20190115_120740.mp4.00_00_56_10.Still001-Copy.jpg

351 ms

10052009263-scaled.jpg

10052009263-scaled.jpg

642 ms

02032008131.jpg

02032008131.jpg

181 ms

IMG-20120716-00059-scaled.jpg

IMG-20120716-00059-scaled.jpg

93 ms

logo-1.jpg

logo-1.jpg

96 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

102 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

102 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

142 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

143 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

86 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

166 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

166 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

166 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

167 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

166 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

166 ms

who.ashx

who.ashx

320 ms

Accessibility Review

thomsonrail.com accessibility score

85

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

thomsonrail.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

thomsonrail.com 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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

thomsonrail.com

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