Tools & Wizards About Us
mtrx.travel screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

mtrx.travel

Book train tickets – Travel Stockholm to Gothenburg | VR

Page Load Speed

2.6 sec in total

First Response

267 ms

Resources Loaded

1.8 sec

Page Rendered

560 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 267 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

mtrx.travel performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value19.9 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value3,650 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.255

48/100

15%

TTI (Time to Interactive)

Value20.5 s

2/100

10%

Network Requests Diagram

en

267 ms

css

136 ms

gtm.js

76 ms

insight.min.js

38 ms

widget.js

31 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 44% of them (25 requests) were addressed to the original Mtrx.travel, 11% (6 requests) were made to Assetscdn-wchat.eu.freshchat.com and 5% (3 requests) were made to Static.klaviyo.com. The less responsive or slowest element that took the longest time to load (735 ms) belongs to the original domain Mtrx.travel.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.3 kB (7%)

Content Size

3.9 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mtrx.travel main page is 3.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 102.2 kB

  • Original 125.3 kB
  • After minification 125.3 kB
  • After compression 23.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 102.2 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 152.2 kB

  • Original 2.6 MB
  • After minification 2.5 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. Mtrx images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 19.6 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 1.0 MB

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

-2%

Potential reduce by 1.3 kB

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

Requests Breakdown

Number of requests can be reduced by 38 (72%)

Requests Now

53

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 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 33 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

en

en

267 ms

css

css

136 ms

gtm.js

gtm.js

76 ms

insight.min.js

insight.min.js

38 ms

widget.js

widget.js

31 ms

1b1a43e60823d44bbdff.css

1b1a43e60823d44bbdff.css

312 ms

fa4697fa1407c3ee2c7c.css

fa4697fa1407c3ee2c7c.css

37 ms

polyfills-70d8d9b71cdaeed482a8.js

polyfills-70d8d9b71cdaeed482a8.js

335 ms

webpack-8b8db2da4488f03975c9.js

webpack-8b8db2da4488f03975c9.js

57 ms

framework-8919cd72989a675aa6ee.js

framework-8919cd72989a675aa6ee.js

51 ms

main-079a1ed60b5c948fa2fe.js

main-079a1ed60b5c948fa2fe.js

56 ms

_app-49a3e7d8f271b3238575.js

_app-49a3e7d8f271b3238575.js

103 ms

487-2e1a66c4d81ef2d567c4.js

487-2e1a66c4d81ef2d567c4.js

66 ms

3221-62bca27ebe5ec0ab8f22.js

3221-62bca27ebe5ec0ab8f22.js

72 ms

4712-756a7ea798347f3f258e.js

4712-756a7ea798347f3f258e.js

131 ms

index-823fb18d41adf1004f02.js

index-823fb18d41adf1004f02.js

131 ms

_buildManifest.js

_buildManifest.js

131 ms

_ssgManifest.js

_ssgManifest.js

131 ms

widget.css

widget.css

497 ms

552 ms

insight.beta.min.js

insight.beta.min.js

13 ms

insight_tag_errors.gif

insight_tag_errors.gif

152 ms

8ee56a825b2d235e6c93bd73244ff5067fd2c0c5_5zb9rka.jpg

8ee56a825b2d235e6c93bd73244ff5067fd2c0c5_5zb9rka.jpg

423 ms

ab509b4d2da86a45cdb65182b1b27845c129429e.png

ab509b4d2da86a45cdb65182b1b27845c129429e.png

420 ms

13399baccca43afa3f36c92c55cb8ef29a166488_4tusT7W.jpg

13399baccca43afa3f36c92c55cb8ef29a166488_4tusT7W.jpg

68 ms

d23a5af901989bb97575d7da7baabe39a7a623c2.png

d23a5af901989bb97575d7da7baabe39a7a623c2.png

735 ms

appstore.0579882c328fd7181a65a00b244dfbfa.svg

appstore.0579882c328fd7181a65a00b244dfbfa.svg

71 ms

google-play.16e4669ad74f1f7fd106e36e4da91de3.svg

google-play.16e4669ad74f1f7fd106e36e4da91de3.svg

95 ms

js

js

90 ms

js

js

52 ms

hotjar-1224308.js

hotjar-1224308.js

122 ms

bat.js

bat.js

76 ms

klaviyo.js

klaviyo.js

115 ms

insight_tag_errors.gif

insight_tag_errors.gif

68 ms

fender_analytics.739eafc699de20b4c3bb.js

fender_analytics.739eafc699de20b4c3bb.js

26 ms

static.047f24ade89e4aff54a9.js

static.047f24ade89e4aff54a9.js

26 ms

runtime.de3587c9054d415a20c1.js

runtime.de3587c9054d415a20c1.js

5 ms

sharedUtils.52f9c435f5e232af1a21.js

sharedUtils.52f9c435f5e232af1a21.js

13 ms

modules.84f80a92c39bbd76564a.js

modules.84f80a92c39bbd76564a.js

27 ms

315416a1b0751a16fc4fac5e7af041a4930caf1b.png

315416a1b0751a16fc4fac5e7af041a4930caf1b.png

47 ms

e46cdeaa25dee3c25014e3c2d795a69901c77197_TaiuJiJ.jpg

e46cdeaa25dee3c25014e3c2d795a69901c77197_TaiuJiJ.jpg

45 ms

vendor.d64d219ca4493f67a3970efc52d51c86.css

vendor.d64d219ca4493f67a3970efc52d51c86.css

47 ms

vendor.93df72b05c8ea64a54740654e7f35ab9.js

vendor.93df72b05c8ea64a54740654e7f35ab9.js

54 ms

237.js

237.js

151 ms

chunk.bd09cfc41d14adc79418.css

chunk.bd09cfc41d14adc79418.css

150 ms

fd-messaging.8b9a3833c11e50975e6a.css

fd-messaging.8b9a3833c11e50975e6a.css

148 ms

fd-messaging.4d9de9e68a8209957595.js

fd-messaging.4d9de9e68a8209957595.js

148 ms

Archivo-Regular.woff

Archivo-Regular.woff

372 ms

Archivo-Bold.woff

Archivo-Bold.woff

400 ms

MTRXHeadline-Regular.woff

MTRXHeadline-Regular.woff

308 ms

landing

landing

191 ms

fbevents.js

fbevents.js

32 ms

5525491.js

5525491.js

53 ms

2148648075347372

2148648075347372

153 ms

5525491

5525491

52 ms

clarity.js

clarity.js

18 ms

c.gif

c.gif

38 ms

Accessibility Review

mtrx.travel accessibility score

95

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.

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

mtrx.travel best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

mtrx.travel SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a valid hreflang

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

High

Tap targets are not sized appropriately

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: