8.3 sec in total
312 ms
6.7 sec
1.4 sec
Click here to check amazing Lafer content. Otherwise, check out these important facts you probably never knew about lafer.it
ARMADI ELETTRICI PER CARPENTERIA QUADRI ELETTRICI | Power Center Distribuzione | Motor Control Center a cassetti fissi o estraibili | Automazione | Server | Inox
Visit lafer.itWe analyzed Lafer.it page load time and found that the first response time was 312 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lafer.it performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value11.1 s
0/100
25%
Value26.2 s
0/100
10%
Value2,750 ms
3/100
30%
Value0.739
6/100
15%
Value39.2 s
0/100
10%
312 ms
445 ms
1956 ms
641 ms
532 ms
Our browser made a total of 188 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Lafer.it, 92% (173 requests) were made to Lafer.com and 3% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Lafer.com.
Page size can be reduced by 4.0 MB (29%)
14.0 MB
10.0 MB
In fact, the total size of Lafer.it main page is 14.0 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. Only a small number of websites need less resources to load. Images take 9.2 MB which makes up the majority of the site volume.
Potential reduce by 150.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. 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 150.5 kB or 87% of the original size.
Potential reduce by 266.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. Lafer images are well optimized though.
Potential reduce by 1.6 MB
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 1.6 MB or 67% of the original size.
Potential reduce by 2.0 MB
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. Lafer.it needs all CSS files to be minified and compressed as it can save up to 2.0 MB or 87% of the original size.
Number of requests can be reduced by 127 (72%)
177
50
The browser has sent 177 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lafer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 96 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
lafer.it
312 ms
lafer.it
445 ms
www.lafer.com
1956 ms
fketx.css
641 ms
fketx.css
532 ms
fketx.css
326 ms
fketx.css
317 ms
fketx.css
523 ms
fketx.css
415 ms
fketx.css
636 ms
fketx.css
535 ms
fketx.css
625 ms
fketx.css
639 ms
fketx.css
643 ms
fketx.css
643 ms
fketx.css
731 ms
style.css
733 ms
fketx.css
734 ms
fketx.css
738 ms
fketx.css
742 ms
fketx.css
745 ms
fketx.css
837 ms
fketx.css
941 ms
fketx.css
1356 ms
fketx.css
843 ms
fketx.css
846 ms
fketx.css
1184 ms
fketx.css
946 ms
fketx.css
1158 ms
css
36 ms
fketx.css
951 ms
fketx.css
1046 ms
fketx.css
1047 ms
fketx.css
1057 ms
fketx.css
1152 ms
fketx.css
1154 ms
stub.js
27 ms
iubenda_cs.js
48 ms
fketx.js
1265 ms
wp-sentry-browser.min.js
4 ms
hooks.min.js
1058 ms
i18n.min.js
1057 ms
api.js
36 ms
index.js
957 ms
index.js
951 ms
core.min.js
1379 ms
main.min.js
1304 ms
accordion.min.js
1180 ms
menu.min.js
1170 ms
dom-ready.min.js
1169 ms
a11y.min.js
1082 ms
autocomplete.min.js
1080 ms
controlgroup.min.js
1077 ms
checkboxradio.min.js
1078 ms
button.min.js
1078 ms
datepicker.min.js
1078 ms
mouse.min.js
991 ms
resizable.min.js
990 ms
draggable.min.js
988 ms
dialog.min.js
984 ms
droppable.min.js
979 ms
progressbar.min.js
978 ms
selectable.min.js
887 ms
sortable.min.js
882 ms
slider.min.js
875 ms
spinner.min.js
781 ms
tooltip.min.js
780 ms
tabs.min.js
1000 ms
effect.min.js
904 ms
effect-blind.min.js
904 ms
effect-bounce.min.js
896 ms
effect-clip.min.js
795 ms
effect-drop.min.js
795 ms
effect-explode.min.js
858 ms
effect-fade.min.js
847 ms
effect-fold.min.js
780 ms
effect-highlight.min.js
782 ms
effect-pulsate.min.js
777 ms
effect-size.min.js
779 ms
effect-scale.min.js
871 ms
empty.html
244 ms
effect-shake.min.js
440 ms
effect-slide.min.js
440 ms
effect-transfer.min.js
440 ms
doubletaptogo.js
438 ms
modernizr.min.js
426 ms
jquery.appear.js
619 ms
hoverIntent.min.js
621 ms
counter.js
620 ms
easypiechart.js
620 ms
mixitup.js
620 ms
jquery.prettyPhoto.js
618 ms
jquery.fitvids.js
657 ms
jquery.flexslider-min.js
657 ms
mediaelement-and-player.min.js
753 ms
mediaelement-migrate.min.js
656 ms
wp-mediaelement.min.js
654 ms
infinitescroll.min.js
653 ms
jquery.waitforimages.js
763 ms
jquery.form.min.js
762 ms
waypoints.min.js
762 ms
jplayer.min.js
759 ms
bootstrap.carousel.js
759 ms
NaPecZTIAOhVxoMyOr9n_E7fdM3mCA.ttf
43 ms
NaPDcZTIAOhVxoMyOr9n_E7ffGjEGIVzZg.ttf
125 ms
NaPDcZTIAOhVxoMyOr9n_E7ffAzHGIVzZg.ttf
217 ms
NaPDcZTIAOhVxoMyOr9n_E7ffBzCGIVzZg.ttf
218 ms
NaPDcZTIAOhVxoMyOr9n_E7ffHjDGIVzZg.ttf
219 ms
NaPDcZTIAOhVxoMyOr9n_E7ffEDBGIVzZg.ttf
218 ms
skrollr.js
822 ms
Chart.min.js
614 ms
jquery.easing.1.3.js
611 ms
abstractBaseClass.js
612 ms
jquery.countdown.js
612 ms
jquery.multiscroll.min.js
611 ms
jquery.justifiedGallery.min.js
720 ms
bigtext.js
637 ms
jquery.sticky-kit.min.js
635 ms
owl.carousel.min.js
636 ms
typed.js
634 ms
jquery.carouFredSel-6.2.1.min.js
634 ms
lemmon-slider.min.js
718 ms
jquery.fullPage.min.js
637 ms
jquery.mousewheel.min.js
633 ms
jquery.touchSwipe.min.js
642 ms
jquery.isotope.min.js
635 ms
packery-mode.pkgd.min.js
649 ms
jquery.stretch.js
547 ms
imagesloaded.js
546 ms
rangeslider.min.js
547 ms
jquery.event.move.js
547 ms
jquery.twentytwenty.js
550 ms
swiper.min.js
546 ms
default_dynamic.js
619 ms
default.js
844 ms
js_composer_front.min.js
634 ms
qode-like.min.js
614 ms
wp-polyfill.min.js
634 ms
index.js
584 ms
fontawesome-webfont.woff
612 ms
close_side_menu_dark.png
608 ms
it.png
608 ms
en.png
643 ms
es.png
644 ms
fr.png
682 ms
lafer_group_spa_2024-1.webp
638 ms
700x300_home14.jpg
638 ms
700x300_home142.jpg
830 ms
700x300_home143.jpg
831 ms
700x300_home144.jpg
845 ms
700x300_plus-1.jpg
812 ms
700x300_home145.jpg
735 ms
700x300_home149.jpg
736 ms
700x300_home148.jpg
735 ms
700x300_home146.jpg
734 ms
700x300_home147.jpg
830 ms
700x300_home1411.jpg
802 ms
700x300_plus.jpg
734 ms
smartenergycopper_home.jpg
833 ms
700x300_home1414.jpg
728 ms
lafergialla_singole1.jpg
720 ms
lafergialla_singole_1803.jpg
1033 ms
lafergialla_singole_18034.jpg
933 ms
lafergialla_singole_18032.jpg
838 ms
lafergialla_singole_18033.jpg
943 ms
lafergialla20217.jpg
730 ms
NWS_Lafer_Smontati_immagine_copertina_home-1030x562.png
1042 ms
nuova_serie_cmpt_plus_easy630_plus.png
836 ms
fast-one_lafer.webp
935 ms
testata_perche_lafer1-1030x551.jpg
945 ms
smart_energy-copper-5000A.jpg
840 ms
fast-one-3D-300x49.png
938 ms
LAFER_QUICK_1600x1400.jpg
922 ms
LAFER_SLIM_1600x1400.jpg
921 ms
LAFER_EASY630_1600x1400.jpg
844 ms
LAFER_COMPACT_1600x1400.jpg
938 ms
LAFER_AUTOMATION_2018_1600x1400.jpg
924 ms
LAFER_LAFERACK_1600x1400.jpg
911 ms
LAFER_MC_CUB_1600x1400.jpg
909 ms
LAFER_ME_CUB-2.0_1600x1400.jpg
841 ms
LAFER_ACCIAIO_BIS_1600x1400.jpg
843 ms
lafer.jpg
938 ms
recaptcha__en.js
178 ms
lafer2-1.jpg
749 ms
certificazioni-cesi.png
750 ms
certificazionilafer.png
742 ms
lafer_group_spa_2024_footer_4.png
738 ms
certificazioni.png
739 ms
lafer.it 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-hidden="true"] elements contain focusable descendents
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
[id] attributes on active, focusable elements are not unique
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.
lafer.it best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
lafer.it 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
IT
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lafer.it can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that Lafer.it 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.
lafer.it
Open Graph data is detected on the main page of Lafer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: