15.5 sec in total
292 ms
14.8 sec
389 ms
Welcome to sanangel.com.co homepage info - get ready to check San Angel best content for Colombia right away, or after learning these important things about sanangel.com.co
Floristería en Medellín - Flores Medellín a Domicilio | San Angel. Encontrará Flores, Floristeria Poblado, Envigado, Bello
Visit sanangel.com.coWe analyzed Sanangel.com.co page load time and found that the first response time was 292 ms and then it took 15.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.
sanangel.com.co performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value3.4 s
66/100
25%
Value8.6 s
17/100
10%
Value1,970 ms
8/100
30%
Value0.021
100/100
15%
Value14.4 s
9/100
10%
292 ms
703 ms
404 ms
125 ms
152 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 75% of them (79 requests) were addressed to the original Sanangel.com.co, 9% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Sanangel.com.co.
Page size can be reduced by 227.2 kB (22%)
1.0 MB
809.7 kB
In fact, the total size of Sanangel.com.co main page is 1.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. Images take 419.7 kB which makes up the majority of the site volume.
Potential reduce by 173.7 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 173.7 kB or 83% of the original size.
Potential reduce by 4.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. San Angel images are well optimized though.
Potential reduce by 17.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 32.0 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. Sanangel.com.co needs all CSS files to be minified and compressed as it can save up to 32.0 kB or 16% of the original size.
Number of requests can be reduced by 69 (78%)
89
20
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of San Angel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
sanangel.com.co
292 ms
sanangel.com.co
703 ms
wp-emoji-release.min.js
404 ms
js
125 ms
ja0a52h1da
152 ms
gtm.js
239 ms
fbevents.js
46 ms
jquery.min.js
81 ms
jquery.min.js
491 ms
ea3165e2849aa345e2aa144e27f975f7.js
418 ms
962c6d8ce0242eb10571549abf2a9cf3.js
425 ms
39d4d697e6f4f1eaaa398e27012771ff.js
431 ms
de289597177551290448d617842320a8.js
448 ms
a3af1408c2de0932d8627c7c027d5f16.js
637 ms
888821e60a051526fa6297f0ca45d67c.js
777 ms
a772b64d6b0d5f6bbbcb7fe30b8adbc1.js
787 ms
38f81eb3af65b57c39003b961ca65395.js
794 ms
63aaf34fbb77947c73633ba3a520cabf.js
806 ms
gtm4wp-form-move-tracker.js
854 ms
gtm4wp-woocommerce-classic.js
1009 ms
gtm4wp-woocommerce-enhanced.js
1141 ms
aaf3b8c05e4ec9895e8efbad70a31d56.js
1156 ms
af257254eb9a90521bc99234bcfea63a.js
1157 ms
b7cf071773b931028c86c4b98140be90.js
1174 ms
22d034036301230c2a27373b79f0fbc6.js
1224 ms
aa6b9b32170ee99c45707d6eec3a4007.js
1378 ms
f91836aaf4391c8833827dbd309fbe1d.js
1504 ms
17bf3fe67e8f268c14aa2535018b1e1f.js
1520 ms
e04fd29443ce7ae2a5d995be117aac5a.js
1517 ms
2cc622fe30c1b1b302ebfe94460b0145.js
1558 ms
4310d47d611099cec17f50130552c0c4.js
1582 ms
dfe2d10acce66af418a43adf60544069.js
1743 ms
7aeaf487f0566ee74691ea24b4dcfbf8.js
1872 ms
8ce498d44da21aa6dfc9889a7c9faf76.js
1897 ms
26972770ab46a2efbfa28459ba8d1a67.js
1887 ms
0353ba1f784b433e3dc9ab939bfdefb3.js
2061 ms
3118a0ee4775aea14a3cb0385b1bff26.js
1953 ms
8e48db1a0d3889c9e2dcbd781d025ca6.js
2247 ms
c9a948ace7aaded999c74970a5cd6d02.js
2240 ms
c9190264e3686a2a4e286f25d06c1662.js
2251 ms
1a927b474763dbebffe1cf7b61d9fd9a.js
2265 ms
75e3c0fd93e180bc208b602bf162f28a.js
2316 ms
popper.min.js
46 ms
bootstrap.min.js
60 ms
zoom.js
2426 ms
clarity.js
19 ms
bootstrap.min.css
29 ms
92579cf59733722420d2e67e7427d6b0.js
2348 ms
js_composer.min.css
609 ms
style.min.css
485 ms
wc-blocks-vendors-style.css
378 ms
wc-blocks-style.css
492 ms
classic-themes.min.css
361 ms
styles.css
369 ms
woo-custom-related-products-public.css
368 ms
woocommerce-layout.css
371 ms
woocommerce-smallscreen.css
365 ms
woocommerce.css
368 ms
frontend.min.css
370 ms
style.min.css
370 ms
style.css
482 ms
frontend.css
384 ms
owl.carousel.min.css
364 ms
fonts.css
365 ms
css
38 ms
css
57 ms
css
60 ms
css
61 ms
fontawesome.css
370 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
20 ms
fontawesome-webfont.woff
737 ms
fa-solid-900.woff
39 ms
fa-regular-400.woff
61 ms
fa-brands-400.woff
76 ms
woocommerce.css
371 ms
style.css
365 ms
js_composer_tta.min.css
495 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff
4 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff
36 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtU.woff
48 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_qiTXtHA_w.woff
50 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_k-UXtHA_w.woff
50 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_gGUXtHA_w.woff
77 ms
0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqs.woff
49 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqs.woff
48 ms
animate.min.css
365 ms
cropped-logo-san-angel-1.png
379 ms
floristerias-medellin-1.jpg
632 ms
evora-new-1-300x300.jpg
514 ms
agata-24-3-300x300.jpg
505 ms
destellos-2-300x300.jpg
492 ms
presente-new-300x300.jpg
493 ms
universo-300x300.jpg
874 ms
reino-de-sue%C3%B1os-300x300.jpg
1613 ms
amo-amor-new-300x300.jpg
987 ms
corazon-corazon-2-floristerias-300x300.jpg
1016 ms
boton-cajas-de-rosas.jpg
882 ms
boton-bouquets.jpg
1029 ms
boton-arreglos.jpg
1235 ms
rosas-blancas.jpg
1523 ms
1200px-Instagram_logo.svg_-185x67.png
1349 ms
BANNER-10-Anos2-1.jpg
1782 ms
RAZONES-PARA-COMPRAR.jpg
1516 ms
payupagosseguros-1-e1577501765127.png
1747 ms
c.gif
9 ms
sanangel.com.co 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.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
sanangel.com.co 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
sanangel.com.co SEO score
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 Sanangel.com.co 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 Sanangel.com.co 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.
sanangel.com.co
Open Graph data is detected on the main page of San Angel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: