3.7 sec in total
410 ms
3 sec
341 ms
Welcome to trilex.de homepage info - get ready to check Trilex best content for Germany right away, or after learning these important things about trilex.de
Viele gute Gründe mit dem trilex zu fahren: Entdecken Sie die Oberlausitz und das Zittauer Gebirge - im Dreiländereck! Ihr Ticket können Sie bequem im Zug kaufen.
Visit trilex.deWe analyzed Trilex.de page load time and found that the first response time was 410 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
trilex.de performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value5.1 s
24/100
25%
Value4.7 s
68/100
10%
Value410 ms
67/100
30%
Value1.145
1/100
15%
Value6.6 s
57/100
10%
410 ms
880 ms
299 ms
600 ms
894 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Trilex.de, 95% (39 requests) were made to Laenderbahn.com and 2% (1 request) were made to Zugsammen.de. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Laenderbahn.com.
Page size can be reduced by 305.1 kB (9%)
3.5 MB
3.2 MB
In fact, the total size of Trilex.de main page is 3.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. 45% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 121.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. This page needs HTML code to be minified as it can gain 44.4 kB, which is 29% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 121.4 kB or 81% of the original size.
Potential reduce by 183.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. Trilex images are well optimized though.
Potential reduce by 12 B
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.
Potential reduce by 176 B
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. Trilex.de has all CSS files already compressed.
We found no issues to fix!
28
28
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trilex. According to our analytics all requests are already optimized.
trilex.de
410 ms
880 ms
28e536db24e859fb5e52e6f8d9037fb2.css
299 ms
b74e8bb281a508488cbffaba43969e78.js
600 ms
du-willst-einen-job-im-trilex-der-dich-bewegt.jpg
894 ms
Website_Startseite_Slider_Newsletter_2_tlx.jpg
375 ms
Website_Teaser_Startseite_trilex_doksy_1440x510px.jpg
296 ms
Header_KuMa0124.jpg
398 ms
Baustellenuebersicht-1.png
868 ms
NET_IN_Header_1180x510_Fruehling-RZ1.jpg
670 ms
Dynamo-Dresden-Teaser-trilex.png
1076 ms
teaser-trilex-ausflugstipp-Zittauer-Schmalspurbahn.jpg
398 ms
Website_Kachel_newsletter_2_1252x661_tlx.jpg
473 ms
Baustellen-Update-1.png
497 ms
ZVON_DIM_FahrgastTV_Jubilaeumswoche_1252-x-661.png
496 ms
trilex-Ausflug_Zittauer-Schmalspurbahn_Tipp_Oybin.jpg
572 ms
Website_Kachel_trilex_doksy_1252x661.jpg
596 ms
trilex_ausflug_wroclaw_tipp_zwerge.jpg
597 ms
Newsletter-trilex-klein.jpg
671 ms
2021_trilex_flohagena-13.jpg
696 ms
Thema-Prospekte-bestellen-TLX.jpg
696 ms
V4A7718.jpg
768 ms
logo-h17.png
739 ms
logo.png
764 ms
flag-cs.jpg
765 ms
flag-pl.jpg
836 ms
home-icon-sprite.png
837 ms
home-icon-bottom-sprite.png
862 ms
netinera-bg.png
864 ms
netinera-logo.png
935 ms
roboto-condensed-v18-latin-ext_latin-regular.woff
697 ms
roboto-condensed-v18-latin-ext_latin-300.woff
704 ms
roboto-condensed-v18-latin-ext_latin-700.woff
723 ms
titillium-web-v8-latin-ext_latin-700.woff
728 ms
titillium-web-v8-latin-ext_latin-600.woff
799 ms
titillium-web-v8-latin-ext_latin-regular.woff
799 ms
titillium-web-v8-latin-ext_latin-300.woff
800 ms
fontawesome-webfont.woff
822 ms
roboto-condensed-v18-latin-ext_latin-300italic.woff
826 ms
roboto-condensed-v18-latin-ext_latin-italic.woff
895 ms
roboto-condensed-v18-latin-ext_latin-700italic.woff
897 ms
trilex.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
trilex.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
trilex.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trilex.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Trilex.de 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.
trilex.de
Open Graph data is detected on the main page of Trilex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: