5.5 sec in total
327 ms
5 sec
200 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 327 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
trilex.de performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value6.9 s
7/100
25%
Value8.0 s
21/100
10%
Value4,780 ms
0/100
30%
Value0.047
99/100
15%
Value14.7 s
8/100
10%
327 ms
201 ms
23 ms
96 ms
186 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 79% of them (45 requests) were addressed to the original Trilex.de, 5% (3 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Trilex.de.
Page size can be reduced by 424.6 kB (48%)
888.2 kB
463.6 kB
In fact, the total size of Trilex.de main page is 888.2 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. 45% of websites need less resources to load. Javascripts take 386.0 kB which makes up the majority of the site volume.
Potential reduce by 41.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. This page needs HTML code to be minified as it can gain 5.6 kB, which is 11% 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 41.5 kB or 79% of the original size.
Potential reduce by 13.8 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 253.8 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 253.8 kB or 66% of the original size.
Potential reduce by 115.5 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. Trilex.de needs all CSS files to be minified and compressed as it can save up to 115.5 kB or 83% of the original size.
Number of requests can be reduced by 29 (57%)
51
22
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trilex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
trilex.de
327 ms
201 ms
css
23 ms
screen.css
96 ms
jquery-ui-1.10.3.custom.min.css
186 ms
tinymce.css
188 ms
lb.css
241 ms
font-awesome.min.css
189 ms
jquery.min.js
371 ms
spinners.js
191 ms
lightview.js
370 ms
jquery.scrollto.js
277 ms
jquery.ui.custom.min.js
552 ms
live-fahrplan.js
277 ms
js.js
278 ms
lightview.css
396 ms
socialmedia.js
350 ms
baustelle.jpg
105 ms
Breslau_Wroclaw_Kulturhauptstadt_TLX1_trilex.jpg
184 ms
Goerlitz_Winter_DaecherAltstadt_NikolaiSchmidt_web.jpg
103 ms
Zmek-SchlossLiberec.jpg
184 ms
Katzensprung-Tickets3.jpg
105 ms
shade-bottom.png
104 ms
oc80.png
149 ms
sprite.png
152 ms
anMUvcNT0H1YN4FII8wpr4e2tK5W43RXgBRKkM4A5Qg.ttf
61 ms
anMUvcNT0H1YN4FII8wprzsSLeNQG2cy_mKit6iEdYs.ttf
61 ms
7XUFZ5tgS-tD6QamInJTcU3KvHLhcNjEHFQzwNtdMQY.ttf
62 ms
fontawesome-webfont.woff
241 ms
box.png
148 ms
partner-vvo.png
238 ms
partner-zvon.png
237 ms
partner-doprava.png
239 ms
partner-lib.png
251 ms
left_right.png
242 ms
top_bottom.png
323 ms
d.jpg
321 ms
cz.jpg
323 ms
pfeil-down.png
324 ms
menu.png
325 ms
lb-chooser.png
94 ms
1174_3_trilexinnenIV.jpg
317 ms
866_3_Trilex14_140515FH0163m.jpg
585 ms
867_3_Zittau.jpg
586 ms
bottom.png
404 ms
bottomright.png
405 ms
piwik.js
480 ms
analytics.js
32 ms
etc_data.php
3380 ms
socialmedia.css
94 ms
sprite.png
366 ms
blank.gif
462 ms
cal.png
462 ms
linkid.js
10 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
435 ms
collect
25 ms
print.css
94 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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
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
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 description is not detected on the main page of Trilex. 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: