2.9 sec in total
539 ms
2.2 sec
155 ms
Welcome to limora.com homepage info - get ready to check Limora best content for Switzerland right away, or after learning these important things about limora.com
Entdecke Oldtimer Ersatzteile für zahlreiche Modelle in unserem Onlineshop ✓ große Auswahl ✓ professionelle Beratung ✓ schnelle Lieferung ✓ beste Qualität ► Jetzt bestellen!
Visit limora.comWe analyzed Limora.com page load time and found that the first response time was 539 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
limora.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value5.3 s
21/100
25%
Value4.6 s
70/100
10%
Value230 ms
86/100
30%
Value0
100/100
15%
Value6.1 s
63/100
10%
539 ms
271 ms
186 ms
186 ms
185 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 94% of them (58 requests) were addressed to the original Limora.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (714 ms) belongs to the original domain Limora.com.
Page size can be reduced by 596.1 kB (56%)
1.1 MB
464.0 kB
In fact, the total size of Limora.com 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 588.8 kB which makes up the majority of the site volume.
Potential reduce by 26.6 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 26.6 kB or 80% of the original size.
Potential reduce by 1.6 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. Limora images are well optimized though.
Potential reduce by 444.2 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 444.2 kB or 75% of the original size.
Potential reduce by 123.7 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. Limora.com needs all CSS files to be minified and compressed as it can save up to 123.7 kB or 85% of the original size.
Number of requests can be reduced by 47 (80%)
59
12
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Limora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.limora.com
539 ms
styles.css
271 ms
colors.css
186 ms
widgets.css
186 ms
custom.css
185 ms
adjustments.css
185 ms
mirasvit_searchautocomplete.css
186 ms
mirasvit_searchindex.css
278 ms
prototype.js
452 ms
ccard.js
275 ms
validation.js
276 ms
builder.js
277 ms
effects.js
358 ms
dragdrop.js
364 ms
controls.js
367 ms
slider.js
367 ms
js.js
364 ms
form.js
448 ms
menu.js
477 ms
translate.js
477 ms
cookies.js
478 ms
jquery.min.js
543 ms
underscore.js
535 ms
backbone.js
538 ms
form.js
540 ms
autocomplete.js
542 ms
event.js
561 ms
element.js
622 ms
ajax.js
625 ms
form.js
627 ms
dropdown.js
628 ms
modernizr.js
629 ms
fake-link.js
636 ms
test-css.js
709 ms
cookies.js
712 ms
ga.js
714 ms
cart.js
713 ms
wishlist.js
540 ms
slideshow.js
562 ms
analytics.js
23 ms
31130_Moritz_Reif_Hamburg.jpg
109 ms
logo_en.png
108 ms
38539_1000x300.jpg
354 ms
38518_1000x300.jpg
442 ms
38515_1000x300.jpg
281 ms
de.gif
93 ms
gb.gif
180 ms
fr.gif
178 ms
it.gif
180 ms
nl.gif
268 ms
es.gif
270 ms
lupe.png
272 ms
loader.gif
355 ms
collect
28 ms
535 ms
collect
76 ms
dropdown_arrow.gif
300 ms
slide_arrow_right.png
301 ms
slide_arrow_left.png
369 ms
ga-audiences
31 ms
warenkorb.png
90 ms
print.css
90 ms
limora.com 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-*] attributes do not match their roles
ARIA IDs are not unique
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
limora.com 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
Missing source maps for large first-party JavaScript
limora.com 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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Limora.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Limora.com 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.
limora.com
Open Graph description is not detected on the main page of Limora. 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: