12.2 sec in total
1.2 sec
10.8 sec
160 ms
Click here to check amazing Elinox content for Brazil. Otherwise, check out these important facts you probably never knew about elinox.com.br
Cantoneiras, bobinas, chapas, barras e tubos de aço inox. Materiais de qualidade e à pronta entrega para seu projeto. Fale com a Elinox!
Visit elinox.com.brWe analyzed Elinox.com.br page load time and found that the first response time was 1.2 sec and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
elinox.com.br performance score
name
value
score
weighting
Value16.0 s
0/100
10%
Value17.0 s
0/100
25%
Value25.5 s
0/100
10%
Value2,800 ms
3/100
30%
Value0.011
100/100
15%
Value37.7 s
0/100
10%
1246 ms
70 ms
497 ms
495 ms
373 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 75% of them (76 requests) were addressed to the original Elinox.com.br, 14% (14 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Elinox.com.br.
Page size can be reduced by 1.8 MB (59%)
3.0 MB
1.2 MB
In fact, the total size of Elinox.com.br main page is 3.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. 55% of websites need less resources to load. CSS take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 179.9 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 179.9 kB or 85% of the original size.
Potential reduce by 3.8 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. Elinox images are well optimized though.
Potential reduce by 366.6 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 366.6 kB or 72% of the original size.
Potential reduce by 1.2 MB
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. Elinox.com.br needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 87% of the original size.
Number of requests can be reduced by 62 (73%)
85
23
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elinox. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
elinox.com.br
1246 ms
gtm.js
70 ms
wp-emoji-release.min.js
497 ms
swiper.min.css
495 ms
slider-pro.min.css
373 ms
style.min.css
616 ms
js
34 ms
styles.css
373 ms
dinamize.css
646 ms
email-before-download-public.css
733 ms
slick.min.css
743 ms
slick-theme.min.css
769 ms
exad-styles.min.css
1134 ms
css
70 ms
front.min.css
891 ms
default.min.css
1015 ms
elementor-icons.min.css
1226 ms
frontend-legacy.min.css
1113 ms
frontend.min.css
1627 ms
font-awesome.min.css
1263 ms
magnific-popup.min.css
1265 ms
nucleo-outline.css
1726 ms
nucleo-mini.css
1668 ms
style.css
2203 ms
css
19 ms
fontawesome.min.css
1759 ms
solid.min.css
1515 ms
regular.min.css
1753 ms
feather-icon-style.min.css
2004 ms
smartslider.min.css
2036 ms
jquery.min.js
2214 ms
jquery-migrate.min.js
2121 ms
dinamize.js
2248 ms
front.min.js
2393 ms
js
35 ms
n2.min.js
2607 ms
smartslider-frontend.min.js
2866 ms
ss-simple.min.js
2548 ms
w-arrow-image.min.js
2655 ms
animations.min.css
2677 ms
cherry-js-core.min.js
2727 ms
jquery.sticky-sidebar.js
2923 ms
swiper.jquery.min.js
3112 ms
jquery.slider-pro.min.js
3146 ms
regenerator-runtime.min.js
3014 ms
wp-polyfill.min.js
3143 ms
index.js
2972 ms
email-before-download-public.js
3022 ms
exad-scripts.min.js
3180 ms
cherry-post-formats.min.js
3106 ms
hoverIntent.min.js
3089 ms
anime.min.js
2999 ms
tilter.js
2918 ms
theme-script.js
3167 ms
webpack.runtime.min.js
3081 ms
frontend-modules.min.js
2999 ms
waypoints.min.js
2871 ms
core.min.js
3017 ms
swiper.min.js
3019 ms
share-link.min.js
2830 ms
dialog.min.js
2804 ms
frontend.min.js
2895 ms
preloaded-modules.min.js
2772 ms
js
106 ms
logotipo.png
2411 ms
banner-institucional.jpg
3047 ms
banner-tubo-schedules.jpg
3042 ms
banner-barras-redondas.jpg
3042 ms
chapas.jpg
2925 ms
tubos.jpg
2924 ms
barras.jpg
2725 ms
analytics.js
87 ms
305894_2136.js
165 ms
S6uyw4BMUTPHjx4wWw.ttf
43 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
67 ms
S6u8w4BMUTPHh30AXC-v.ttf
122 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
142 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
141 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
142 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
141 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
142 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
141 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
143 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
163 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
143 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
143 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
144 ms
nucleo-mini.woff
3573 ms
collect
44 ms
collect
28 ms
fa-solid-900.woff
3388 ms
ga-audiences
27 ms
fa-regular-400.woff
3086 ms
feather.woff
3153 ms
fontawesome-webfont.woff
3181 ms
bobinas.jpg
2966 ms
cantoneiras.jpg
3336 ms
ISO-328x203.jpg
3119 ms
Exercito-328x203.jpg
3018 ms
Abrablin-328x203.jpg
3057 ms
Petrobras-CRC-328x203.jpg
3072 ms
elinox.com.br 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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
elinox.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Issues were logged in the Issues panel in Chrome Devtools
elinox.com.br SEO score
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elinox.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Elinox.com.br 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.
elinox.com.br
Open Graph data is detected on the main page of Elinox. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: