4.4 sec in total
726 ms
3.4 sec
347 ms
Click here to check amazing Santive content for Brazil. Otherwise, check out these important facts you probably never knew about santive.com
Somos uma empresa moderna que busca sempre superar os objetivos propostos para cada projeto, desenvolvendo-os com qualidade excepcional e assim atingindo a
Visit santive.comWe analyzed Santive.com page load time and found that the first response time was 726 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
santive.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value6.7 s
7/100
25%
Value11.7 s
4/100
10%
Value2,700 ms
3/100
30%
Value0.265
46/100
15%
Value21.6 s
1/100
10%
726 ms
26 ms
325 ms
132 ms
261 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 41% of them (41 requests) were addressed to the original Santive.com, 20% (20 requests) were made to Static.xx.fbcdn.net and 9% (9 requests) were made to Sumome-140a.kxcdn.com. The less responsive or slowest element that took the longest time to load (838 ms) belongs to the original domain Santive.com.
Page size can be reduced by 1.8 MB (76%)
2.4 MB
569.5 kB
In fact, the total size of Santive.com main page is 2.4 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. 80% 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. CSS take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 32.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. This page needs HTML code to be minified as it can gain 6.7 kB, which is 15% 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 32.9 kB or 76% of the original size.
Potential reduce by 14.5 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. Santive images are well optimized though.
Potential reduce by 687.7 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 687.7 kB or 71% of the original size.
Potential reduce by 1.1 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. Santive.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 93% of the original size.
Number of requests can be reduced by 59 (60%)
98
39
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Santive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
www.santive.com
726 ms
css
26 ms
bootstrap.css
325 ms
bootstrap-responsive.css
132 ms
style.css
261 ms
sc-commerce.css
133 ms
jquery.js
327 ms
jquery.placeholder.min.js
133 ms
bxslider.js
198 ms
bootstrap.js
347 ms
flick.css
263 ms
www.santive.com
838 ms
styles.css
345 ms
styles.css
380 ms
jquery.js
454 ms
jquery-migrate.min.js
387 ms
scrollTo.js
390 ms
jquery.form.min.js
390 ms
mailchimp.js
390 ms
core.min.js
452 ms
datepicker.js
583 ms
load.sumome.com
377 ms
scripts.js
400 ms
wp-embed.min.js
402 ms
wp-emoji-release.min.js
146 ms
ga.js
38 ms
base.js
37 ms
hotjar-26879.js
341 ms
logo.png
84 ms
logo-verde.jpg
84 ms
santive-commerce.png
338 ms
ecommerce-banner.png
84 ms
site-banner.png
85 ms
sistemas-banner.png
337 ms
dados-online-ate-a-compra-460x350.gif
364 ms
success-graph-1013tm-pic-2393-460x350.jpg
364 ms
shutterstock_roi-graphs-460x350.jpg
362 ms
spank-logo-160x120.png
335 ms
moderno-brasil-logo-160x120.jpg
361 ms
olga-logo-160x120.png
361 ms
ebblindados-logo-160x120.png
361 ms
ec-taubate-logo-160x120.png
518 ms
superlife-suplementos.jpg
407 ms
gtm.js
59 ms
all.js
54 ms
texture.png
482 ms
__utm.gif
43 ms
b
37 ms
b
20 ms
collect
275 ms
widgets.js
282 ms
268 ms
310 ms
ping
77 ms
glyphicons-halflings.png
178 ms
ajax-loader.gif
178 ms
xd_arbiter.php
45 ms
xd_arbiter.php
179 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
168 ms
widget_v2.134.js
37 ms
__$$__stringtable_lang_pt_BR.js
42 ms
like_box.php
119 ms
__tt.gif
22 ms
IWXAbM4pe57.css
45 ms
whsuYM0JyRK.css
47 ms
6AfFAsilC-W.css
67 ms
q68gy-v_YMF.js
68 ms
VvsfEObxnnn.js
52 ms
0wM5s1Khldu.js
51 ms
1bNoFZUdlYZ.js
92 ms
OloiM1PZafe.js
67 ms
LTv6ZK-5zxz.js
112 ms
1FCa-btixu2.js
96 ms
Oagsvfb4VWi.js
95 ms
pObvZSrFc_4.js
97 ms
Kt4tkgSRvHH.js
96 ms
H3EKDTObx05.js
96 ms
eR-qA8bp1RM.js
143 ms
service.js
73 ms
service.js
32 ms
service.js
267 ms
service.js
267 ms
service.js
267 ms
sme-popup.css
186 ms
390749_447028452058467_1653519160_n.jpg
279 ms
935434_447027568725222_2130762187_n.png
238 ms
12227596_1583198615340290_3201109572558165216_n.jpg
219 ms
12049441_523246184508450_6705290551133519818_n.jpg
221 ms
12631446_937143933033382_6844296396499527796_n.jpg
218 ms
12745449_1677672422516439_3038618510939111280_n.jpg
238 ms
1928860_1546528595668755_3561169355241199657_n.jpg
239 ms
10391380_10153962309223917_5847728937646009954_n.jpg
221 ms
wL6VQj7Ab77.png
163 ms
s7jcwEQH7Sx.png
162 ms
gxbPuQdXIZP.png
154 ms
css
159 ms
sumome-welcome-popup.css
114 ms
sumome-share-client.css
34 ms
sumome-smartbar-popup.css
62 ms
I6-MnjEovm5.js
4 ms
pQrUxxo5oQp.js
6 ms
santive.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
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
No form fields have multiple labels
Form elements do not have associated labels
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.
santive.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
Issues were logged in the Issues panel in Chrome Devtools
santive.com 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 uses legible font sizes
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Santive.com 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 Santive.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.
santive.com
Open Graph description is not detected on the main page of Santive. 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: