Tools & Wizards About Us
faberglass.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

faberglass.com

Used machinery for the glass industry, Faberglass, Terni

Page Load Speed

3.2 sec in total

First Response

251 ms

Resources Loaded

2.6 sec

Page Rendered

345 ms

faberglass.com screenshot

About Website

Welcome to faberglass.com homepage info - get ready to check Faberglass best content right away, or after learning these important things about faberglass.com

Faberglass, researches and sells used machinery for the glass industry. Best quality and good prices.

Visit faberglass.com

Key Findings

We analyzed Faberglass.com page load time and found that the first response time was 251 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

faberglass.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,110 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

www.faberglass.com

251 ms

minified.js

138 ms

focus-within-polyfill.js

374 ms

polyfill.min.js

424 ms

bootstrap-features.24d4529b.bundle.min.js

370 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Faberglass.com, 46% (21 requests) were made to Static.wixstatic.com and 43% (20 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 359.4 kB (34%)

Content Size

1.0 MB

After Optimization

684.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Faberglass.com main page is 1.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. 60% of websites need less resources to load. Images take 552.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 346.2 kB

  • Original 443.2 kB
  • After minification 441.4 kB
  • After compression 97.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. 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 346.2 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 12.5 kB

  • Original 552.5 kB
  • After minification 540.0 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. Faberglass images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 671 B

  • Original 48.4 kB
  • After minification 48.3 kB
  • After compression 47.7 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.

Requests Breakdown

Number of requests can be reduced by 9 (25%)

Requests Now

36

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faberglass. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.faberglass.com

www.faberglass.com

251 ms

minified.js

minified.js

138 ms

focus-within-polyfill.js

focus-within-polyfill.js

374 ms

polyfill.min.js

polyfill.min.js

424 ms

bootstrap-features.24d4529b.bundle.min.js

bootstrap-features.24d4529b.bundle.min.js

370 ms

main.24eb524d.bundle.min.js

main.24eb524d.bundle.min.js

370 ms

lodash.min.js

lodash.min.js

389 ms

react.production.min.js

react.production.min.js

389 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

388 ms

wix-perf-measure.bundle.min.js

wix-perf-measure.bundle.min.js

383 ms

react-dom.production.min.js

react-dom.production.min.js

385 ms

staticCss.min.css

staticCss.min.css

361 ms

9beee4_b610dd165dac40368d1a7af233c0def0~mv2.png

9beee4_b610dd165dac40368d1a7af233c0def0~mv2.png

888 ms

thunderbolt

thunderbolt

887 ms

9beee4_b9eb078d43d04d9e82b37c08f2895559~mv2.jpg

9beee4_b9eb078d43d04d9e82b37c08f2895559~mv2.jpg

890 ms

5bfb6f_c2ae26a3c5004bca9ea2b860a535f4ab~mv2.png

5bfb6f_c2ae26a3c5004bca9ea2b860a535f4ab~mv2.png

642 ms

5bfb6f_ff73ca63250240b2a3c975834afa9356~mv2.png

5bfb6f_ff73ca63250240b2a3c975834afa9356~mv2.png

697 ms

logoimdddddmprof.png

logoimdddddmprof.png

888 ms

49c1daaca6ff444aa34f5ecc66d8ae1f.jpg

49c1daaca6ff444aa34f5ecc66d8ae1f.jpg

855 ms

ff2c0fa76a5347f3b0f298d9feb685de.jpg

ff2c0fa76a5347f3b0f298d9feb685de.jpg

856 ms

f22d3579840e47d8bf1a793790603d98.jpg

f22d3579840e47d8bf1a793790603d98.jpg

847 ms

9beee4_01871273ac04401798d4065640b9d294~mv2.jpg

9beee4_01871273ac04401798d4065640b9d294~mv2.jpg

819 ms

9beee4_ae50f75ff86c456bbd55de084f15ff5f~mv2.jpg

9beee4_ae50f75ff86c456bbd55de084f15ff5f~mv2.jpg

1061 ms

9beee4_b01d42cc4d134371bf8fe49d5cc5a4d2~mv2.jpg

9beee4_b01d42cc4d134371bf8fe49d5cc5a4d2~mv2.jpg

819 ms

9beee4_53f26b59369c4408aaee41a8a2806a4e~mv2.jpg

9beee4_53f26b59369c4408aaee41a8a2806a4e~mv2.jpg

885 ms

9beee4_80c515be14884a9cbcf6ec7a858abe24~mv2.jpg

9beee4_80c515be14884a9cbcf6ec7a858abe24~mv2.jpg

927 ms

9beee4_6e551670110a43029f39636d7cb66968~mv2.jpg

9beee4_6e551670110a43029f39636d7cb66968~mv2.jpg

919 ms

9beee4_58dab89f425448669286232fcbe40fe1~mv2.jpg

9beee4_58dab89f425448669286232fcbe40fe1~mv2.jpg

965 ms

9beee4_0846b4ef115d481eaedc0572ae63e92e~mv2.jpg

9beee4_0846b4ef115d481eaedc0572ae63e92e~mv2.jpg

1024 ms

9beee4_57f2e81ca2c84459aa11361b68b7612b~mv2.jpg

9beee4_57f2e81ca2c84459aa11361b68b7612b~mv2.jpg

1070 ms

9beee4_75e78cce2a3f458faa30c64fcc4195db~mv2.jpg

9beee4_75e78cce2a3f458faa30c64fcc4195db~mv2.jpg

1081 ms

9beee4_3346864175534eb286e7737425bbbbce~mv2.jpg

9beee4_3346864175534eb286e7737425bbbbce~mv2.jpg

1126 ms

9beee4_09555c983bbc401f85dd869a7dcf5ade~mv2.png

9beee4_09555c983bbc401f85dd869a7dcf5ade~mv2.png

1171 ms

9beee4_6333957429654876865a5d8c7a63c72d~mv2.png

9beee4_6333957429654876865a5d8c7a63c72d~mv2.png

1206 ms

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

122 ms

4d716cea-5ba0-437a-b5a8-89ad159ea2be.woff

4d716cea-5ba0-437a-b5a8-89ad159ea2be.woff

63 ms

e56ecb6d-da41-4bd9-982d-2d295bec9ab0.woff

e56ecb6d-da41-4bd9-982d-2d295bec9ab0.woff

14 ms

ProximaNovaW05-Regular.woff

ProximaNovaW05-Regular.woff

119 ms

thunderbolt

thunderbolt

302 ms

deprecation-en.v5.html

deprecation-en.v5.html

12 ms

bolt-performance

bolt-performance

117 ms

deprecation-style.v5.css

deprecation-style.v5.css

24 ms

right-arrow.svg

right-arrow.svg

57 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

64 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

49 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

49 ms

Accessibility Review

faberglass.com accessibility score

87

Accessibility Issues

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

faberglass.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

faberglass.com SEO score

98

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faberglass.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Faberglass.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.

Social Sharing Optimization

faberglass.com

Open Graph data is detected on the main page of Faberglass. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: