3.2 sec in total
308 ms
2.7 sec
192 ms
Click here to check amazing LEXO content for Germany. Otherwise, check out these important facts you probably never knew about lexo.ch
LEXO repariert Computer (PCs), Notebooks (Laptops) und Server Vor-Ort oder per Fernwartung. LEXO konfiguriert Client-Server Netzwerk Infrastrukturen auf Basis von Windows, Apple OSX und Linux. LEXO bi...
Visit lexo.chWe analyzed Lexo.ch page load time and found that the first response time was 308 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
lexo.ch performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value11.5 s
0/100
25%
Value9.3 s
13/100
10%
Value2,420 ms
5/100
30%
Value0.001
100/100
15%
Value12.0 s
16/100
10%
308 ms
543 ms
104 ms
207 ms
285 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 82% of them (46 requests) were addressed to the original Lexo.ch, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Lexo.ch.
Page size can be reduced by 432.7 kB (53%)
823.1 kB
390.4 kB
In fact, the total size of Lexo.ch main page is 823.1 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. 35% of websites need less resources to load. Javascripts take 434.4 kB which makes up the majority of the site volume.
Potential reduce by 27.9 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 6.2 kB, which is 17% 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 27.9 kB or 77% of the original size.
Potential reduce by 5.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. LEXO images are well optimized though.
Potential reduce by 339.1 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 339.1 kB or 78% of the original size.
Potential reduce by 60.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. Lexo.ch needs all CSS files to be minified and compressed as it can save up to 60.3 kB or 87% of the original size.
Number of requests can be reduced by 31 (63%)
49
18
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LEXO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
lexo.ch
308 ms
www.lexo.ch
543 ms
jquery.mCustomScrollbar.min.css
104 ms
style.css
207 ms
superfish.css
285 ms
superfish-navbar.css
285 ms
jquery-1.11.2.js
1003 ms
createHTML5elements.js
292 ms
functions.js
399 ms
j-functions.js
305 ms
hoverIntent.js
380 ms
jquery.form.js
472 ms
jquery.livequery.min.js
389 ms
jquery.validate.js
601 ms
superfish.js
472 ms
jquery.mCustomScrollbar.concat.min.js
678 ms
analytics.js
123 ms
browser.png
645 ms
bg.png
118 ms
panel_close.png
119 ms
int_pan_aktuelles_hover.png
119 ms
int_pan_fernwartung_hover.png
118 ms
int_pan_ticket_hover.png
117 ms
int_pan_team_hover.png
118 ms
sdk.js
78 ms
content_bg.png
150 ms
header_bg.png
136 ms
logo.png
141 ms
menu_first_inactive_bg.png
141 ms
subemenu_line.png
149 ms
submenu_arrow.png
137 ms
menu_item_bg.png
230 ms
menu_last_inactive_bg.png
231 ms
panel.png
235 ms
it-support.png
523 ms
netzwerke.png
248 ms
vor-ort.png
247 ms
windows-linux-osx.png
324 ms
firewall.png
325 ms
hosting.png
331 ms
fernwartung.png
346 ms
int_pan_aktuelles.png
347 ms
int_pan_fernwartung.png
511 ms
int_pan_ticket.png
417 ms
int_pan_team.png
428 ms
myriadpro-regular-webfont.woff
545 ms
myriadpro-cond-webfont.woff
555 ms
myriadpro-semibold-webfont.woff
606 ms
myriadpro-light-webfont.woff
525 ms
132 ms
xd_arbiter.php
39 ms
collect
63 ms
collect
55 ms
update.js
31 ms
like.php
90 ms
LVx-xkvaJ0b.png
12 ms
lexo.ch accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
lexo.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
lexo.ch 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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lexo.ch 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 Lexo.ch 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.
lexo.ch
Open Graph description is not detected on the main page of LEXO. 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: