5.5 sec in total
1.5 sec
3.6 sec
357 ms
Welcome to lexican.de homepage info - get ready to check LexiCan best content for Germany right away, or after learning these important things about lexican.de
Mit lexiCan Wiki-Software Wissen und Information komfortabel dokumentieren, effektiv ordnen und sicher abrufen. Jetzt kostenlos testen!
Visit lexican.deWe analyzed Lexican.de page load time and found that the first response time was 1.5 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
lexican.de performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value7.0 s
6/100
25%
Value5.8 s
49/100
10%
Value100 ms
98/100
30%
Value0.001
100/100
15%
Value4.4 s
84/100
10%
1478 ms
69 ms
314 ms
402 ms
313 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 76% of them (37 requests) were addressed to the original Lexican.de, 8% (4 requests) were made to Google-analytics.com and 4% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Lexican.de.
Page size can be reduced by 457.2 kB (41%)
1.1 MB
666.1 kB
In fact, the total size of Lexican.de main page is 1.1 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. 40% of websites need less resources to load. Javascripts take 623.4 kB which makes up the majority of the site volume.
Potential reduce by 49.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 12.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 49.5 kB or 69% of the original size.
Potential reduce by 2.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. LexiCan images are well optimized though.
Potential reduce by 405.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 405.1 kB or 65% of the original size.
Potential reduce by 0 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.
Number of requests can be reduced by 25 (56%)
45
20
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LexiCan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
lexican.de
1478 ms
gtm.js
69 ms
media,_plg_system_browserupdatewarning,_css,_BrowserUpdateWarning.css+plugins,_system,_rokbox,_assets,_styles,_rokbox.css+libraries,_gantry,_css,_grid-responsive.css+templates,_rt_lexican,_css-compiled,_bootstrap.css+templates,_rt_lexican,_css-compiled,_master-30aeb216101e84ac9d80685adfe53bec.css+templates,_rt_lexican,_css,_master-webkit.css+templates,_rt_lexican,_css-compiled,_demo-30aeb216101e84ac9d80685adfe53bec.css+templates,_rt_lexican,_css-compiled,_mediaqueries.css+templates,_rt_lexican,_css-compiled,_menu.css+templates,_rt_lexican,_css,_rt_lexican-custom.css+templates,_rt_lexican,_roksprocket,_layouts,_features,_themes,_showcase,_showcase.css.pagespeed.cc.hvBkJxj3d7.css
314 ms
mootools-core.js
402 ms
core.js
313 ms
mootools-more.js
603 ms
BrowserUpdateWarning.js
338 ms
jquery.min.js
424 ms
jquery-noconflict.js
425 ms
jquery-migrate.min.js
425 ms
caption.js
426 ms
rokbox.js
507 ms
bootstrap.min.js
505 ms
gantry-totop.js
508 ms
browser-engines.js
515 ms
rokmediaqueries.js
514 ms
rokmediaqueries.js
691 ms
sidemenu.js
692 ms
mootools-mobile.js
692 ms
rokmediaqueries.js
695 ms
roksprocket.js
695 ms
moofx.js
706 ms
features.js
722 ms
showcase.js
721 ms
analytics.js
31 ms
conversion_async.js
48 ms
linkid.js
8 ms
ec.js
9 ms
collect
13 ms
30 ms
collect
61 ms
43 ms
ga-audiences
21 ms
view.php
412 ms
view.php
416 ms
xlogo.png.pagespeed.ic.lAHyK7g7cJ.png
148 ms
bg.png
204 ms
xbox_1_neu-version8.png.pagespeed.ic.riRu5IK2Ka.jpg
146 ms
90x70xdr_hoech_100x70.jpg.pagespeed.ic.Oyo_XmB8TH.jpg
146 ms
bg.png
110 ms
icon-chrome.png
114 ms
icon-ie.png
111 ms
icon-safari.png
110 ms
icon-firefox.png
112 ms
icon-opera.png
166 ms
opensans-bold-webfont.woff
204 ms
opensans-light-webfont.woff
315 ms
fontawesome-webfont.woff
390 ms
opensans-regular-webfont.woff
296 ms
lexican.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.
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
lexican.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
lexican.de SEO score
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 Lexican.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 Lexican.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.
lexican.de
Open Graph description is not detected on the main page of LexiCan. 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: