6.7 sec in total
773 ms
5.5 sec
480 ms
Welcome to fuso.in homepage info - get ready to check FUSO best content for India right away, or after learning these important things about fuso.in
FUSO is one of the country’s preferred players in processed glass solutions. Get the complete range of high quality glasses for automotive, speciality, architectural & suntuitive solutions.
Visit fuso.inWe analyzed Fuso.in page load time and found that the first response time was 773 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fuso.in performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value5.8 s
15/100
25%
Value11.1 s
6/100
10%
Value210 ms
89/100
30%
Value0
100/100
15%
Value12.0 s
16/100
10%
773 ms
88 ms
277 ms
487 ms
479 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 80% of them (70 requests) were addressed to the original Fuso.in, 9% (8 requests) were made to Use.typekit.net and 2% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Fuso.in.
Page size can be reduced by 1.6 MB (24%)
7.0 MB
5.3 MB
In fact, the total size of Fuso.in main page is 7.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. 70% of websites need less resources to load. Images take 6.7 MB which makes up the majority of the site volume.
Potential reduce by 71.4 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 28.3 kB, which is 35% 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 71.4 kB or 88% of the original size.
Potential reduce by 1.6 MB
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, FUSO needs image optimization as it can save up to 1.6 MB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.3 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 10.0 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. Fuso.in needs all CSS files to be minified and compressed as it can save up to 10.0 kB or 12% of the original size.
Number of requests can be reduced by 27 (38%)
72
45
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUSO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
fuso.in
773 ms
aos.css
88 ms
bootstrap.css
277 ms
all.css
487 ms
animate.css
479 ms
icofont.css
511 ms
style.css
523 ms
bootstrapValidator.min.css
492 ms
industry-font.css
541 ms
owl-carousel.css
710 ms
icon
93 ms
css
116 ms
slick.css
711 ms
slick-animate.css
739 ms
jquery.min.js
767 ms
popper.min.js
763 ms
bootstrap.min.js
843 ms
wow.min.js
956 ms
jquery.easing.1.3.js
942 ms
jquery.waypoints.js
1068 ms
jquery.counterup.min.js
1079 ms
custom.js
1079 ms
bootstrapValidator.min.js
1109 ms
owl-carousel.js
1277 ms
slick.js
1203 ms
slick-animations.js
1283 ms
aos.js
76 ms
tti.min.js
54 ms
tccl.min.js
45 ms
p.css
33 ms
logo_color.svg
511 ms
Untitled-1.jpg
1554 ms
mobile3.png
1731 ms
Untitled-2.jpg
1499 ms
mobile2.png
1948 ms
Untitled-3.jpg
1515 ms
mobile1.png
1984 ms
home_products_architecture.jpg
1730 ms
home_products_speciality.jpg
2225 ms
home_products_automotive.jpg
1790 ms
pioneer.png
2209 ms
028.png
2664 ms
056.png
2724 ms
019.png
2409 ms
airport.png
3201 ms
Picture1.png
2434 ms
Path210.svg
2466 ms
logoArtboard-1.png
2633 ms
logoArtboard-2.png
2675 ms
logoArtboard-3.png
2704 ms
logoArtboard-4.png
2860 ms
logoArtboard-5.png
2892 ms
logoArtboard-6.png
2897 ms
logoArtboard-7.png
2940 ms
logoArtboard-8.png
2959 ms
logoArtboard-9.png
3028 ms
logoArtboard-10.png
2964 ms
logoArtboard-11.png
2956 ms
logoArtboard-12.png
2906 ms
logoArtboard-13.png
2895 ms
logoArtboard-14.png
3018 ms
d
185 ms
d
186 ms
d
715 ms
d
719 ms
d
719 ms
d
720 ms
d
818 ms
d
817 ms
gok-H7zzDkdnRel8-DQ6KAXJ69wP1tGnf4ZGhUcd.otf
44 ms
flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf
99 ms
fa-solid-900.woff
3033 ms
fa-regular-400.woff
3049 ms
fa-brands-400.woff
3010 ms
logoArtboard-15.png
2929 ms
logoArtboard-16.png
2929 ms
logoArtboard-17.png
3036 ms
logoArtboard-18.png
2095 ms
logoArtboard-19.png
2082 ms
logoArtboard-20.png
2106 ms
logoArtboard-21.png
1944 ms
logoArtboard-22.png
1945 ms
logoArtboard-23.png
1986 ms
logoArtboard-24.png
1876 ms
logo_white.svg
1842 ms
footer_bg3.jpg
1678 ms
cta_bg2.png
1688 ms
fuso.in 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.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
fuso.in 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fuso.in 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
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 Fuso.in 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 Fuso.in 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.
fuso.in
Open Graph data is detected on the main page of FUSO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: