11.1 sec in total
247 ms
7.1 sec
3.8 sec
Click here to check amazing Fire Glass content for United States. Otherwise, check out these important facts you probably never knew about fireglass.com
Technical Glass Products is the recognized leader in fire-rated glass and framing. Explore the world of beautifully safe solutions for innovative architecture.
Visit fireglass.comWe analyzed Fireglass.com page load time and found that the first response time was 247 ms and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fireglass.com performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value13.5 s
0/100
25%
Value8.0 s
22/100
10%
Value3,060 ms
2/100
30%
Value0.158
73/100
15%
Value16.5 s
5/100
10%
247 ms
223 ms
352 ms
227 ms
632 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 60% of them (88 requests) were addressed to the original Fireglass.com, 7% (10 requests) were made to Use.typekit.net and 4% (6 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Fireglass.com.
Page size can be reduced by 307.2 kB (54%)
573.0 kB
265.8 kB
In fact, the total size of Fireglass.com main page is 573.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 291.2 kB which makes up the majority of the site volume.
Potential reduce by 138.8 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 138.8 kB or 81% of the original size.
Potential reduce by 17.4 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. Obviously, Fire Glass needs image optimization as it can save up to 17.4 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 136.4 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 136.4 kB or 47% of the original size.
Potential reduce by 14.6 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. Fireglass.com needs all CSS files to be minified and compressed as it can save up to 14.6 kB or 33% of the original size.
Number of requests can be reduced by 46 (36%)
127
81
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fire Glass. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
fireglass.com
247 ms
fireglass.com
223 ms
www.fireglass.com
352 ms
main-2022.min.css
227 ms
ionicons.min.css
632 ms
css
732 ms
wdk8osr.css
727 ms
api.js
632 ms
jquery-3.0.0.min.js
706 ms
jquery.easing.min.js
746 ms
modernizr.min.js
808 ms
velocity.min.js
1029 ms
classie.min.js
860 ms
gsap.min.js
1029 ms
ScrollMagic.js
627 ms
jquery.ScrollMagic.js
722 ms
debug.addIndicators.js
718 ms
animation.gsap.js
707 ms
lodash.min.js
845 ms
jquery.hoverIntent.js
768 ms
navigation.js
769 ms
ts.js
613 ms
conversion.js
759 ms
otSDKStub.js
716 ms
css
543 ms
css
555 ms
p.css
137 ms
hotjar-844340.js
1494 ms
gtm.js
1504 ms
allegion.png
506 ms
fireglass-logo-red-2022.png
1402 ms
FireLite-logo-color.svg
1416 ms
fireRated.svg
1407 ms
hoseStream.svg
1402 ms
positivePressure.svg
1398 ms
intertek.svg
1404 ms
UL.svg
1822 ms
bulletResistant.svg
1698 ms
energyEfficient.svg
1701 ms
heatBarrier.svg
1815 ms
hurricaneRated.svg
1826 ms
impactRated.svg
1702 ms
loadBearing.svg
2002 ms
stainlessSteel.svg
2015 ms
tempRise-filled.svg
3190 ms
forcedEntry.svg
2016 ms
search.png
2013 ms
search.svg
2010 ms
hero.webp
3569 ms
home-video-link.webp
2432 ms
number-one.png
2430 ms
video-street-talk.webp
2433 ms
case-study-occidental.webp
3236 ms
homepage-sustainability.webp
3237 ms
Fireglass-3d-00.webp
3214 ms
specify.webp
3212 ms
portfolio.webp
3497 ms
tgp-initiative.webp
3689 ms
support.webp
3688 ms
footer-tgpa-logo.png
3495 ms
facebook.png
3444 ms
twitter.png
3497 ms
linkedin.png
3708 ms
instagram.png
3708 ms
youtube.png
3706 ms
recaptcha__en.js
1983 ms
d
896 ms
d
988 ms
d
988 ms
d
988 ms
d
1119 ms
S6uyw4BMUTPHjx4wWw.ttf
1623 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
2760 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
2863 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
2863 ms
d
1268 ms
d
1388 ms
d
1268 ms
d
1389 ms
footer-tgpf-logo.png
3344 ms
fbevents.js
1917 ms
analytics.js
1601 ms
bat.js
2426 ms
9fd9a7db-c70b-4b97-b528-eb8c55ad28f6.json
877 ms
2026 ms
o.js
260 ms
insight.min.js
1973 ms
footer-allegion-logo.png
2605 ms
header.png
2604 ms
Fireglass-3d-01.webp
2575 ms
Fireglass-3d-02.webp
2567 ms
Fireglass-3d-03.webp
2855 ms
Fireglass-3d-04.webp
2855 ms
modules.cf44a0a6b448df1b035e.js
1690 ms
Fireglass-3d-05.webp
2650 ms
Fireglass-3d-06.webp
2587 ms
js
665 ms
otBannerSdk.js
661 ms
Fireglass-3d-07.webp
2534 ms
Fireglass-3d-08.webp
2529 ms
Fireglass-3d-09.webp
2625 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
1520 ms
Fireglass-3d-10.webp
2462 ms
Fireglass-3d-11.webp
2450 ms
Fireglass-3d-12.webp
2483 ms
Fireglass-3d-13.webp
2432 ms
Fireglass-3d-14.webp
2432 ms
Fireglass-3d-15.webp
2513 ms
Fireglass-3d-16.webp
2090 ms
Fireglass-3d-17.webp
2087 ms
collect
936 ms
682465941853750
854 ms
en.json
305 ms
Fireglass-3d-18.webp
1375 ms
Fireglass-3d-19.webp
1305 ms
Fireglass-3d-20.webp
1285 ms
Fireglass-3d-21.webp
1355 ms
Fireglass-3d-22.webp
1354 ms
Fireglass-3d-23.webp
1347 ms
275 ms
5215616.js
405 ms
collect
942 ms
otFlat.json
444 ms
otPcTab.json
447 ms
Fireglass-3d-24.webp
1074 ms
Fireglass-3d-25.webp
1072 ms
Fireglass-3d-26.webp
1071 ms
Fireglass-3d-27.webp
1211 ms
Fireglass-3d-28.webp
1205 ms
visit-data
1159 ms
Fireglass-3d-29.webp
1065 ms
Fireglass-3d-30.webp
1022 ms
Fireglass-3d-31.webp
1029 ms
Fireglass-3d-32.webp
1048 ms
Fireglass-3d-33.webp
1085 ms
5215616
599 ms
Fireglass-3d-34.webp
889 ms
Fireglass-3d-35.webp
923 ms
Fireglass-3d-36.webp
927 ms
Fireglass-3d-37.webp
925 ms
Fireglass-3d-38.webp
923 ms
Fireglass-3d-39.webp
663 ms
ga-audiences
114 ms
clarity.js
66 ms
88 ms
c.gif
66 ms
fireglass.com 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
fireglass.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fireglass.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fireglass.com 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 Fireglass.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.
fireglass.com
Open Graph data is detected on the main page of Fire Glass. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: