5.6 sec in total
721 ms
4.1 sec
797 ms
Click here to check amazing SANTIAL content. Otherwise, check out these important facts you probably never knew about santial.com
Visite la galería online del artista y disfrute de la visión delicada y particular del mundo que nos rodea en sus trabajos.
Visit santial.comWe analyzed Santial.com page load time and found that the first response time was 721 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
santial.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value15.3 s
0/100
25%
Value13.5 s
2/100
10%
Value430 ms
64/100
30%
Value0.059
98/100
15%
Value21.8 s
1/100
10%
721 ms
405 ms
225 ms
232 ms
637 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 72% of them (67 requests) were addressed to the original Santial.com, 4% (4 requests) were made to Fonts.googleapis.com and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Santial.com.
Page size can be reduced by 1.1 MB (16%)
6.9 MB
5.8 MB
In fact, the total size of Santial.com main page is 6.9 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. 35% of websites need less resources to load. Images take 6.2 MB which makes up the majority of the site volume.
Potential reduce by 60.2 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 60.2 kB or 72% of the original size.
Potential reduce by 641.0 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. SANTIAL images are well optimized though.
Potential reduce by 349.9 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 349.9 kB or 66% of the original size.
Potential reduce by 41.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. Santial.com needs all CSS files to be minified and compressed as it can save up to 41.8 kB or 82% of the original size.
Number of requests can be reduced by 64 (74%)
87
23
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SANTIAL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
santial.com
721 ms
style.css
405 ms
css_browser_selector.js
225 ms
navigation.css
232 ms
jquery.min.js
637 ms
css
23 ms
text-5b2380f8-cd61-cb0a-c775-b21c1b053726.css
231 ms
text.css
321 ms
text.js
329 ms
text-c27cdebe-14f0-8ac7-fef3-909672da1f26.css
335 ms
header-610906b1-ffbb-08c4-2893-5aaba2f7abfc.css
246 ms
text-ccaa5097-50f7-b4b3-4a5d-3440a0417b4c.css
331 ms
header-e2ceb9c8-138e-ee7a-f02a-50499f16f8a1.css
344 ms
text-8e2e489c-6f61-2d2c-b103-abae69bdf733.css
356 ms
text-22c0770f-c15e-5114-142e-695e63947eb8.css
349 ms
jquery.jcarousellite.js
417 ms
jquery.simplemodal.js
441 ms
imagegallery.js
562 ms
imagegallery.css
464 ms
imagegallery.locale-es_ES.js
465 ms
addthis_widget.js
44 ms
navigation-2bfb0a86-d0f6-b3a3-5e37-bf362e90418d.css
526 ms
css
14 ms
header-aabe9597-6c1c-5bc3-4a06-fa5f09292443.css
559 ms
text-9b27f56a-e869-bdb1-2a25-424e4fa7a7da.css
630 ms
text-88fd1ad6-b15c-fa9d-f5d1-3c5a5f8c1edd.css
629 ms
text-be22df71-7b3e-eb0d-3dab-3db521f3a975.css
630 ms
text-774fedb7-372e-ed68-d9c6-b35f599aa2aa.css
649 ms
text-006613a1-aeec-efea-7807-e8769a07b198.css
651 ms
layout.css
665 ms
helpers.js
676 ms
view.js
678 ms
anti_cache.js
653 ms
css
13 ms
css
24 ms
background81.png
126 ms
external-border-none-top-left.png
134 ms
external-border-none-top-right.png
134 ms
external-border-none-top.png
135 ms
external-border-none-top-left2.png
135 ms
external-border-none-top-right2.png
186 ms
external-border-none-left.png
230 ms
external-border-none-left-top.png
231 ms
external-border-none-left-bottom.png
233 ms
external-border-none-right.png
236 ms
external-border-none-right-top.png
231 ms
external-border-none-right-bottom.png
248 ms
external-border-none-bottom-left.png
319 ms
external-border-none-bottom-right.png
335 ms
external-border-none-bottom.png
340 ms
external-border-none-bottom-left2.png
339 ms
external-border-none-bottom-right2.png
336 ms
border-none-top-left.png
351 ms
border-none-top-right.png
419 ms
border-none-top.png
439 ms
border-none-left.png
451 ms
border-none-right.png
451 ms
60a58d64f2340c4926e46d3dcfe10810.png
867 ms
logo.jpg
561 ms
menu-toggle.png
530 ms
published_image_3.jpg
772 ms
border-none-bottom-left.png
553 ms
border-none-bottom-right.png
554 ms
border-none-bottom.png
622 ms
MG_9378.JPG
2027 ms
ATIENZA-009.JPG
1002 ms
TERTULIA.jpg
790 ms
mis-imagenes-236.jpg
1838 ms
IMG_2660.JPG
1396 ms
published_image_0.jpg
1192 ms
300lo.json
85 ms
es.js
22 ms
all.js&version=v2.0
638 ms
widgets.js
90 ms
iHJ27bULqQIvyO7lI2EU_-vvDin1pK8aKteLpeZ5c0A.ttf
18 ms
BLPy8WjUBSi7b4eL1hPWzaCWcynf_cDxXwCLxiixG1c.ttf
63 ms
2chzL5br_YXR3tkyUeYeM-vvDin1pK8aKteLpeZ5c0A.ttf
62 ms
hr7Un5rTZbWMVxBLJvXJaaCWcynf_cDxXwCLxiixG1c.ttf
19 ms
published_image_2.jpg
1280 ms
sh.8e5f85691f9aaa082472a194.html
55 ms
66ebdfcb-f4a0-972f-66d6-8ce09559d48a.thumb.jpg
993 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
128 ms
pixel
16 ms
match-result
6 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.es.html
41 ms
jot
92 ms
144 ms
xd_arbiter.php
211 ms
xd_arbiter.php
441 ms
ping
57 ms
like.php
92 ms
qeKvIRsJabD.js
485 ms
LVx-xkvaJ0b.png
547 ms
santial.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
Links do not have a discernible name
santial.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
santial.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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Santial.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 Santial.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.
santial.com
Open Graph description is not detected on the main page of SANTIAL. 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: