7.5 sec in total
1.3 sec
5.9 sec
408 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 1.3 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fuso.in performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value5.9 s
14/100
25%
Value11.9 s
4/100
10%
Value180 ms
92/100
30%
Value0
100/100
15%
Value12.3 s
15/100
10%
1275 ms
46 ms
260 ms
472 ms
496 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 81% 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 (2.8 sec) belongs to the original domain Fuso.in.
Page size can be reduced by 1.6 MB (23%)
7.2 MB
5.5 MB
In fact, the total size of Fuso.in main page is 7.2 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.9 MB which makes up the majority of the site volume.
Potential reduce by 71.6 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.4 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.6 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.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. 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 26 (37%)
71
45
The browser has sent 71 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 14 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
fuso.in
1275 ms
aos.css
46 ms
bootstrap.css
260 ms
all.css
472 ms
animate.css
496 ms
icofont.css
749 ms
style.css
761 ms
bootstrapValidator.min.css
514 ms
industry-font.css
573 ms
owl-carousel.css
706 ms
icon
43 ms
css
62 ms
slick.css
741 ms
slick-animate.css
768 ms
jquery.min.js
1147 ms
popper.min.js
940 ms
bootstrap.min.js
1318 ms
wow.min.js
996 ms
jquery.easing.1.3.js
1011 ms
jquery.waypoints.js
1020 ms
jquery.counterup.min.js
1216 ms
custom.js
1318 ms
bootstrapValidator.min.js
1319 ms
owl-carousel.js
1319 ms
slick.js
1496 ms
slick-animations.js
1497 ms
aos.js
53 ms
scc-c2.min.js
11 ms
p.css
30 ms
logo_color.svg
342 ms
Untitled-1.jpg
1083 ms
mobile3.png
1373 ms
Untitled-2.jpg
876 ms
mobile2.png
1751 ms
Untitled-3.jpg
1023 ms
mobile1.png
1566 ms
home_products_architecture.jpg
1130 ms
home_products_speciality.jpg
1491 ms
home_products_automotive.jpg
1334 ms
pioneer.png
1892 ms
028.png
2085 ms
056.png
1877 ms
019.png
1968 ms
airport.png
2313 ms
Picture1.png
2037 ms
Path210.svg
2131 ms
logoArtboard-1.png
2143 ms
logoArtboard-2.png
2202 ms
logoArtboard-3.png
2322 ms
logoArtboard-4.png
2333 ms
logoArtboard-5.png
2384 ms
logoArtboard-6.png
2396 ms
logoArtboard-7.png
2443 ms
logoArtboard-8.png
2560 ms
logoArtboard-9.png
2608 ms
logoArtboard-10.png
2582 ms
logoArtboard-11.png
2637 ms
logoArtboard-12.png
2597 ms
logoArtboard-13.png
2525 ms
logoArtboard-14.png
2653 ms
logoArtboard-15.png
2677 ms
logoArtboard-16.png
2763 ms
d
39 ms
d
117 ms
d
157 ms
d
159 ms
d
158 ms
d
158 ms
d
159 ms
d
161 ms
gok-H7zzDkdnRel8-DQ6KAXJ69wP1tGnf4ZGhUcd.otf
158 ms
flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf
162 ms
fa-solid-900.woff
2715 ms
fa-regular-400.woff
2585 ms
fa-brands-400.woff
2585 ms
logoArtboard-17.png
2716 ms
logoArtboard-18.png
2212 ms
logoArtboard-19.png
2126 ms
logoArtboard-20.png
2107 ms
logoArtboard-21.png
2032 ms
logoArtboard-22.png
1816 ms
logoArtboard-23.png
1933 ms
logoArtboard-24.png
1845 ms
logo_white.svg
1835 ms
footer_bg3.jpg
1634 ms
cta_bg2.png
1536 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: