Tools & Wizards About Us
mtrx.travel screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mtrx.travel

Book train tickets – Travel Stockholm to Gothenburg | VR

Page Load Speed

1.8 sec in total

First Response

91 ms

Resources Loaded

1.1 sec

Page Rendered

602 ms

mtrx.travel screenshot

About Website

Welcome to mtrx.travel homepage info - get ready to check Mtrx best content right away, or after learning these important things about mtrx.travel

Boka din resa mellan Göteborg och Stockholm med VR – Det moderna snabbtåget. Tågbolaget med Sveriges nöjdaste kunder enligt Svenskt Kvalitetsindex. Punktligast. Lägst pris. Miljövänligt. Modernt. Grat...

Visit mtrx.travel

Key Findings

We analyzed Mtrx.travel page load time and found that the first response time was 91 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

mtrx.travel performance score

0

Network Requests Diagram

mtrx.travel

91 ms

en

320 ms

css

69 ms

gtm.js

137 ms

insight.min.js

128 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 82% of them (28 requests) were addressed to the original Mtrx.travel, 3% (1 request) were made to Fonts.googleapis.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (394 ms) belongs to the original domain Mtrx.travel.

Page Optimization Overview & Recommendations

Page size can be reduced by 121.8 kB (8%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 101.9 kB

  • Original 125.5 kB
  • After minification 125.4 kB
  • After compression 23.5 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 101.9 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 891.5 kB
  • After minification 891.5 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. Mtrx images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 19.2 kB

  • Original 463.4 kB
  • After minification 463.4 kB
  • After compression 444.2 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

-5%

Potential reduce by 655 B

  • Original 12.1 kB
  • After minification 12.1 kB
  • After compression 11.4 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. Mtrx.travel has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (54%)

Requests Now

28

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mtrx.travel

mtrx.travel

91 ms

en

en

320 ms

css

css

69 ms

gtm.js

gtm.js

137 ms

insight.min.js

insight.min.js

128 ms

widget.js

widget.js

57 ms

43832f6be1326c2798c857e7.js

43832f6be1326c2798c857e7.js

66 ms

d38da1454813898ae7bb.css

d38da1454813898ae7bb.css

47 ms

a64580c403ab819b2324.css

a64580c403ab819b2324.css

62 ms

polyfills-70d8d9b71cdaeed482a8.js

polyfills-70d8d9b71cdaeed482a8.js

360 ms

webpack-2ff6b0df1da61ff3b222.js

webpack-2ff6b0df1da61ff3b222.js

125 ms

framework-8919cd72989a675aa6ee.js

framework-8919cd72989a675aa6ee.js

122 ms

main-079a1ed60b5c948fa2fe.js

main-079a1ed60b5c948fa2fe.js

81 ms

_app-18a584010be964cbb25f.js

_app-18a584010be964cbb25f.js

128 ms

6368-4187510d0ffa2cbfb48f.js

6368-4187510d0ffa2cbfb48f.js

127 ms

1207-8e84797acb4e2f578f88.js

1207-8e84797acb4e2f578f88.js

127 ms

7307-f7fba58fd8b523487321.js

7307-f7fba58fd8b523487321.js

125 ms

7270-1e356d54834533c656af.js

7270-1e356d54834533c656af.js

128 ms

index-9289d232c4bc73498e69.js

index-9289d232c4bc73498e69.js

128 ms

_buildManifest.js

_buildManifest.js

131 ms

_ssgManifest.js

_ssgManifest.js

129 ms

e249b22a20437acd7a9a6f1ba54532fd22bc5ad7_IUXWFB9.png

e249b22a20437acd7a9a6f1ba54532fd22bc5ad7_IUXWFB9.png

55 ms

SuisseIntl-Regular-WebS.woff

SuisseIntl-Regular-WebS.woff

393 ms

SuisseIntl-Medium-WebS.woff

SuisseIntl-Medium-WebS.woff

391 ms

SuisseIntl-SemiBold-WebS.woff

SuisseIntl-SemiBold-WebS.woff

394 ms

SuisseIntl-Bold-WebS.woff

SuisseIntl-Bold-WebS.woff

391 ms

6e19a69fb758abe9efa8fff5e9cb63cde393ef0c_VIYOEl1.png

6e19a69fb758abe9efa8fff5e9cb63cde393ef0c_VIYOEl1.png

58 ms

14eed5ddacbca27c0b2b433720a7f57c5a6859b2_MeBLDqH.png

14eed5ddacbca27c0b2b433720a7f57c5a6859b2_MeBLDqH.png

58 ms

5c7f502bb4ff7e0884aa024d1e2d2485d3d9aa5e_aDqkRRz.png

5c7f502bb4ff7e0884aa024d1e2d2485d3d9aa5e_aDqkRRz.png

60 ms

a160aee2e1ea2cf934aa5fc88f8ee24ae2776550_UwMIibc.png

a160aee2e1ea2cf934aa5fc88f8ee24ae2776550_UwMIibc.png

79 ms

0132da09130ca6fa3bf6e8c1d784e9415a02aeb1_zEF1Hv3.png

0132da09130ca6fa3bf6e8c1d784e9415a02aeb1_zEF1Hv3.png

98 ms

appstore.0579882c328fd7181a65a00b244dfbfa.svg

appstore.0579882c328fd7181a65a00b244dfbfa.svg

112 ms

google-play.16e4669ad74f1f7fd106e36e4da91de3.svg

google-play.16e4669ad74f1f7fd106e36e4da91de3.svg

155 ms

insight_tag_errors.gif

insight_tag_errors.gif

125 ms

SEO Factors

mtrx.travel SEO score

0

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 Mtrx.travel 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 Mtrx.travel 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

mtrx.travel

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