5.7 sec in total
251 ms
4.9 sec
583 ms
Welcome to lexs.org homepage info - get ready to check Lexs best content for Germany right away, or after learning these important things about lexs.org
Visit lexs.orgWe analyzed Lexs.org page load time and found that the first response time was 251 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
lexs.org performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value1.9 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
251 ms
2507 ms
201 ms
294 ms
299 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 54% of them (50 requests) were addressed to the original Lexs.org, 25% (23 requests) were made to Maps.googleapis.com and 9% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Lexs.org.
Page size can be reduced by 567.4 kB (33%)
1.7 MB
1.1 MB
In fact, the total size of Lexs.org main page is 1.7 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. 60% of websites need less resources to load. Images take 903.4 kB which makes up the majority of the site volume.
Potential reduce by 48.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. 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 48.4 kB or 85% of the original size.
Potential reduce by 9.9 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. Lexs images are well optimized though.
Potential reduce by 435.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 435.1 kB or 67% of the original size.
Potential reduce by 73.9 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. Lexs.org needs all CSS files to be minified and compressed as it can save up to 73.9 kB or 81% of the original size.
Number of requests can be reduced by 32 (39%)
82
50
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lexs. 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 from 8 to 1 for CSS and as a result speed up the page load time.
lexs.org
251 ms
www.lexs.org
2507 ms
reset.css
201 ms
template.css
294 ms
joomla.css
299 ms
font-awesome.min.css
309 ms
system.css
235 ms
bootstrap.min.css
310 ms
jquery.min.js
563 ms
jquery-noconflict.js
363 ms
jquery-migrate.min.js
386 ms
caption.js
394 ms
jquery.touchSwipe.min.js
410 ms
jquery.colorbox-min.js
410 ms
script.min.js
464 ms
bootstrap.min.js
489 ms
jquery.cycle2.js
32 ms
jquery.cycle2.carousel.js
32 ms
cookieAccept.js
502 ms
template.js
517 ms
js
76 ms
system.css
296 ms
noise.png
137 ms
switch07.jpg
453 ms
logo-ghost.svg
137 ms
arbeitsplatz.jpg
178 ms
edelstrom.jpg
255 ms
server.jpg
181 ms
kolab.png
236 ms
odoo.svg
238 ms
webdesign.jpg
350 ms
001_aappartel_-_boardinghouse_city_center.png
327 ms
002_fine_first_decor.png
334 ms
003_karins_babytreff.png
338 ms
004_katharina.png
373 ms
005_palliativmedizin_bielefeld.png
444 ms
006_rechtsanwaelte_dr_jur_schulte.png
435 ms
007_schilder_klaus_industrieschilder.png
436 ms
008_stieghorst_garten-_und_landschaftsbau.png
546 ms
009_tattoo_by_johann.png
563 ms
010_tka-intertrans.png
537 ms
011_wd_forklift_service.png
630 ms
terra-hover.png
571 ms
terra.png
569 ms
panda-new-hover.png
646 ms
panda-new.png
645 ms
multimatic-hover.png
675 ms
multimatic.png
679 ms
data-recovery-hover.png
689 ms
data-recovery.png
741 ms
hp-hover.svg
742 ms
hp.svg
751 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
63 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
63 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
65 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
64 ms
fontawesome-webfont.woff
778 ms
1pO9eUAp8pSF8VnRTP3xnvesZW2xOQ-xsNqO47m55DA.woff
65 ms
OLffGBTaF0XFOW1gnuHF0YbN6UDyHWBl620a-IRfuBk.woff
65 ms
7m8l7TlFO-S3VkhHuR0at4bN6UDyHWBl620a-IRfuBk.woff
64 ms
t6Nd4cfPRhZP44Q5QAjcC4bN6UDyHWBl620a-IRfuBk.woff
62 ms
common.js
18 ms
map.js
37 ms
util.js
80 ms
controls.js
77 ms
places_impl.js
76 ms
StaticMapService.GetMapImage
206 ms
onion.js
28 ms
openhand_8_8.cur
118 ms
stats.js
77 ms
css
81 ms
transparent.png
38 ms
ViewportInfoService.GetViewportInfo
71 ms
infowindow.js
21 ms
AuthenticationService.Authenticate
73 ms
PlaceService.GetPlaceDetails
86 ms
google4.png
61 ms
mapcnt6.png
23 ms
sv5.png
32 ms
tmapctrl.png
17 ms
tmapctrl4.png
17 ms
vt
47 ms
vt
51 ms
vt
63 ms
vt
42 ms
vt
44 ms
vt
54 ms
vt
79 ms
vt
88 ms
vt
85 ms
marker.js
48 ms
spotlight-poi.png
13 ms
lexs.org accessibility score
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
Document doesn't have a <title> element
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
lexs.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
lexs.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
N/A
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lexs.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Lexs.org 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.
lexs.org
Open Graph description is not detected on the main page of Lexs. 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: