7.3 sec in total
120 ms
6.9 sec
218 ms
Visit furrer.it now to see the best up-to-date Furrer content and also check out these interesting facts you probably never knew about furrer.it
Furrer S.p.a. Carrara is, since 1939, one of the main leaders in marble and stone projects perfect for interiors and, exteriors, claddings, floorings and facings, for private and commercial purposes.
Visit furrer.itWe analyzed Furrer.it page load time and found that the first response time was 120 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
furrer.it performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value10.1 s
0/100
25%
Value10.1 s
9/100
10%
Value940 ms
30/100
30%
Value0.508
16/100
15%
Value14.8 s
8/100
10%
120 ms
354 ms
286 ms
40 ms
47 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 84% of them (93 requests) were addressed to the original Furrer.it, 5% (6 requests) were made to Cdnjs.cloudflare.com and 3% (3 requests) were made to Cdn.iubenda.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Furrer.it.
Page size can be reduced by 87.5 kB (8%)
1.1 MB
1.1 MB
In fact, the total size of Furrer.it 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. Images take 772.5 kB which makes up the majority of the site volume.
Potential reduce by 61.0 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 13.8 kB, which is 18% 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 61.0 kB or 82% of the original size.
Potential reduce by 899 B
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. Furrer images are well optimized though.
Potential reduce by 6.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 18.8 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. Furrer.it needs all CSS files to be minified and compressed as it can save up to 18.8 kB or 16% of the original size.
Number of requests can be reduced by 86 (92%)
93
7
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Furrer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 49 to 1 for CSS and as a result speed up the page load time.
furrer.it
120 ms
furrer.it
354 ms
index.asp
286 ms
bootstrap.min.css
40 ms
bootstrap-select.min.css
47 ms
style.css
442 ms
layout-home.css
378 ms
jquery.fancybox-1.3.4-min.css
385 ms
slicknav.css
381 ms
jquery-3.3.1.js
36 ms
jquery-migrate-3.0.1.min.js
38 ms
popper.min.js
51 ms
bootstrap.min.js
49 ms
jquery.fancybox.css
376 ms
jquery.fancybox.min.js
515 ms
owl.carousel.min.css
727 ms
owl.carousel.min.js
732 ms
bootstrap-select.min.js
63 ms
SpryCollapsiblePanel.js
746 ms
SpryCollapsiblePanelsShare.css
730 ms
datepicker.css
776 ms
bootstrap-datepicker.js
866 ms
bootstrap4-block-grid.css
1063 ms
jquery.validate.js
1084 ms
jquery.stellar.js
1068 ms
animate.css
1104 ms
wow.min.js
1110 ms
animsition.css
1209 ms
animsition.js
1424 ms
functions-min.js
1403 ms
gsap.min.js
12 ms
CSSRulePlugin.min.js
17 ms
TextPlugin.min.js
165 ms
ScrollToPlugin.min.js
18 ms
ScrollTrigger.min.js
22 ms
DrawSVGPlugin.min.js
1353 ms
stub.js
28 ms
iubenda_cs.js
33 ms
pe-icon-7-stroke.css
1394 ms
settings.css
1225 ms
layers.css
1502 ms
thetis.css
1568 ms
jquery.themepunch.tools.min.js
1677 ms
jquery.themepunch.revolution.min.js
1693 ms
revolution.extension.actions.min.js
1707 ms
revolution.extension.carousel.min.js
1757 ms
revolution.extension.kenburn.min.js
1844 ms
revolution.extension.layeranimation.min.js
1873 ms
revolution.extension.migration.min.js
1992 ms
revolution.extension.navigation.min.js
2017 ms
revolution.extension.parallax.min.js
2027 ms
revolution.extension.slideanims.min.js
2072 ms
revolution.extension.video.min.js
2108 ms
EGSharePage-follow-us.js
1942 ms
furrer.jpg
2074 ms
logo.png
2098 ms
GTAmericaR.woff
1900 ms
GTAmericaM.woff
2229 ms
GTAmericaL.woff
2273 ms
GTAmericaT.woff
2099 ms
GTAmericaBd.woff
2166 ms
base.css
1589 ms
loading.css
1612 ms
fade.css
1854 ms
fade-up.css
1921 ms
fade-up-sm.css
1927 ms
fade-up-lg.css
1969 ms
fade-down.css
1963 ms
fade-down-sm.css
2036 ms
fade-down-lg.css
2205 ms
fade-left.css
2271 ms
fade-left-sm.css
2182 ms
fade-left-lg.css
2115 ms
fade-right.css
2106 ms
fade-right-sm.css
2180 ms
fade-right-lg.css
2295 ms
rotate.css
2259 ms
rotate-sm.css
2187 ms
rotate-lg.css
2130 ms
flip-x.css
2104 ms
flip-x-nr.css
2171 ms
flip-x-fr.css
2286 ms
flip-y.css
2251 ms
flip-y-nr.css
2186 ms
flip-y-fr.css
2107 ms
zoom.css
2090 ms
zoom-sm.css
2157 ms
zoom-lg.css
2289 ms
overlay-slide-top.css
2250 ms
overlay-slide-bottom.css
2207 ms
overlay-slide-left.css
2178 ms
overlay-slide-right.css
2099 ms
printstyle.css
339 ms
gtm.js
73 ms
js
74 ms
bars.svg
393 ms
logo-furrer.svg
390 ms
search.svg
392 ms
HelvNeueCdReg.woff
442 ms
HelvNeueCdMd.woff
434 ms
HelvNeueCdLt.woff
885 ms
HelvNeueCdTh.woff
774 ms
HelvNeueCdBd.woff
512 ms
fontawesome-webfont.woff
969 ms
FidesHN-Bd.woff
820 ms
FidesHN-Md.woff
809 ms
FidesHN.woff
881 ms
FidesHN-Lt.woff
1143 ms
in.php
127 ms
main.js
437 ms
iubenda.js
7 ms
furrer.it accessibility score
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
furrer.it 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
furrer.it SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
![]()
EN
![]()
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Furrer.it can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Furrer.it main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
furrer.it
Open Graph data is detected on the main page of Furrer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: