2.9 sec in total
814 ms
1.7 sec
378 ms
Visit santgar.com now to see the best up-to-date Santgar content for Mexico and also check out these interesting facts you probably never knew about santgar.com
custom description for seo
Visit santgar.comWe analyzed Santgar.com page load time and found that the first response time was 814 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
santgar.com performance score
name
value
score
weighting
Value15.5 s
0/100
10%
Value33.2 s
0/100
25%
Value21.9 s
0/100
10%
Value900 ms
31/100
30%
Value0.139
79/100
15%
Value30.5 s
0/100
10%
814 ms
121 ms
206 ms
250 ms
128 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 94% of them (58 requests) were addressed to the original Santgar.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (814 ms) belongs to the original domain Santgar.com.
Page size can be reduced by 865.5 kB (50%)
1.7 MB
850.0 kB
In fact, the total size of Santgar.com main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 694.3 kB which makes up the majority of the site volume.
Potential reduce by 19.1 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 3.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 19.1 kB or 80% of the original size.
Potential reduce by 23.7 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. Santgar images are well optimized though.
Potential reduce by 484.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 484.3 kB or 70% of the original size.
Potential reduce by 338.3 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. Santgar.com needs all CSS files to be minified and compressed as it can save up to 338.3 kB or 84% of the original size.
Number of requests can be reduced by 38 (68%)
56
18
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Santgar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
santgar.com
814 ms
rokbox.css
121 ms
bootstrap.css
206 ms
master-190e8e119c96157394918bcd1182eef7.css
250 ms
demo-190e8e119c96157394918bcd1182eef7.css
128 ms
mediaqueries.css
125 ms
grid-flexbox-responsive.css
86 ms
menu-dropdown-direction.css
130 ms
menu.css
160 ms
mosaic.css
167 ms
slideshow.css
170 ms
rokajaxsearch.css
170 ms
rokajaxsearch-theme.css
211 ms
jquery.min.js
326 ms
jquery-noconflict.js
212 ms
jquery-migrate.min.js
211 ms
caption.js
242 ms
mootools-core.js
320 ms
core.js
263 ms
mootools-more.js
454 ms
rokbox.js
286 ms
chart.js
285 ms
gantry-totop.js
293 ms
browser-engines.js
356 ms
rokmediaqueries.js
357 ms
rokmediaqueries.js
357 ms
sidemenu.js
359 ms
iframe-height.min.js
364 ms
mootools-mobile.js
370 ms
rokmediaqueries.js
371 ms
roksprocket.js
374 ms
moofx.js
400 ms
roksprocket.request.js
405 ms
mosaic.js
412 ms
mosaic.js
413 ms
features.js
414 ms
slideshow.js
423 ms
rokajaxsearch.js
373 ms
analytics.js
181 ms
formulario.html
141 ms
santgar-logo.png
52 ms
search-icon.png
52 ms
perro1.jpg
125 ms
gato1.jpg
126 ms
buho1.jpg
163 ms
caballo1.jpg
165 ms
banner-oftalvet-nos.jpg
90 ms
productos.jpg
91 ms
enfermedades.jpg
133 ms
distribuidores.jpg
135 ms
bottom-top.png
170 ms
merriweather-regular-webfont.woff
170 ms
merriweather-bold-webfont.woff
185 ms
nexa-bold-webfont.woff
239 ms
nexa-light-webfont.woff
209 ms
estilos1.css
194 ms
css
29 ms
collect
15 ms
fondo.jpg
49 ms
boton.jpg
50 ms
sombra.png
50 ms
K6ngFdK5haaaRGBV8waDwA.ttf
13 ms
santgar.com 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
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
santgar.com 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
santgar.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Santgar.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Santgar.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.
santgar.com
Open Graph description is not detected on the main page of Santgar. 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: