12.5 sec in total
2.3 sec
9.9 sec
301 ms
Welcome to spix.com.br homepage info - get ready to check Spix best content for Brazil right away, or after learning these important things about spix.com.br
spix interactive solutions
Visit spix.com.brWe analyzed Spix.com.br page load time and found that the first response time was 2.3 sec and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
spix.com.br performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value9.5 s
0/100
25%
Value8.0 s
22/100
10%
Value240 ms
85/100
30%
Value0.248
50/100
15%
Value9.6 s
29/100
10%
2299 ms
29 ms
2206 ms
344 ms
76 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 56% of them (54 requests) were addressed to the original Spix.com.br, 19% (18 requests) were made to Maps.google.com and 8% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Spix.com.br.
Page size can be reduced by 807.6 kB (50%)
1.6 MB
796.5 kB
In fact, the total size of Spix.com.br main page is 1.6 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. Javascripts take 922.1 kB which makes up the majority of the site volume.
Potential reduce by 52.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 52.8 kB or 82% of the original size.
Potential reduce by 10.3 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. Spix images are well optimized though.
Potential reduce by 649.8 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 649.8 kB or 70% of the original size.
Potential reduce by 94.8 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. Spix.com.br needs all CSS files to be minified and compressed as it can save up to 94.8 kB or 84% of the original size.
Number of requests can be reduced by 60 (69%)
87
27
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spix. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
spix.com.br
2299 ms
css
29 ms
mootools-core.js
2206 ms
core.js
344 ms
caption.js
76 ms
mootools-more.js
5626 ms
jd.gallery.js
499 ms
jd.gallery.transitions.js
112 ms
css
39 ms
s5_flex_menu.js
1553 ms
s5_flex_menu.css
411 ms
system.css
447 ms
general.css
482 ms
template_default.css
518 ms
template.css
1029 ms
com_content.css
621 ms
editor.css
726 ms
thirdparty.css
1152 ms
multibox.css
761 ms
ajax.css
796 ms
overlay.js
832 ms
multibox.js
1452 ms
s5_responsive_bars.css
1189 ms
s5_responsive_hide_classes.css
1360 ms
s5_responsive.css
1352 ms
custom.css
1394 ms
s5_info_slide.css
1395 ms
s5_info_slide.js
1722 ms
css
41 ms
s5_responsive_mobile_bar.js
1450 ms
js
20 ms
lazy_load.js
817 ms
s5_columns_equalizer.js
1027 ms
system.css
37 ms
s5_background.jpg
45 ms
menu_light.png
45 ms
search_light.png
348 ms
s5_logo.png
487 ms
a1.jpg
2611 ms
a2.jpg
2539 ms
a3.jpg
2111 ms
is1.jpg
693 ms
is2.jpg
650 ms
is3.jpg
823 ms
laptop_ipad_iphone.jpg
1955 ms
s5_header_bg.png
714 ms
facebook.png
749 ms
google.png
786 ms
rss.png
821 ms
s5_search.png
849 ms
s5_menu_bg.png
856 ms
s5_top_row1.png
891 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
14 ms
gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf
10 ms
s5_scroll_arrow.png
835 ms
s5_menu_arrow.png
823 ms
common.js
26 ms
util.js
11 ms
geocoder.js
8 ms
map.js
15 ms
StaticMapService.GetMapImage
80 ms
AuthenticationService.Authenticate
36 ms
GeocodeService.Search
119 ms
onion.js
20 ms
openhand_8_8.cur
33 ms
ViewportInfoService.GetViewportInfo
79 ms
stats.js
20 ms
controls.js
15 ms
transparent.png
34 ms
css
23 ms
google4.png
54 ms
marker.js
31 ms
mapcnt6.png
77 ms
sv5.png
81 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
52 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
52 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
52 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
52 ms
vt
58 ms
loading-bar-black.gif
858 ms
fleche1.png
513 ms
fleche2.png
557 ms
tmapctrl.png
28 ms
cb_scout5.png
29 ms
tmapctrl4.png
30 ms
StaticMapService.GetMapImage
103 ms
ViewportInfoService.GetViewportInfo
29 ms
infowindow.js
14 ms
tack.png
534 ms
vt
16 ms
vt
69 ms
vt
15 ms
vt
17 ms
vt
18 ms
vt
50 ms
vt
44 ms
spix.com.br accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
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.
spix.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
spix.com.br SEO score
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 doesn't use legible font sizes
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spix.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 Spix.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.
spix.com.br
Open Graph description is not detected on the main page of Spix. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: