10.1 sec in total
106 ms
6.4 sec
3.6 sec
Click here to check amazing Visit Sao Miguel content. Otherwise, check out these important facts you probably never knew about visitsaomiguel.com
São Miguel is an amazing green island with subtropical climate. During your holiday in São Miguel you can enjoy lagoons, waterfalls, hot springs and flowers year round.
Visit visitsaomiguel.comWe analyzed Visitsaomiguel.com page load time and found that the first response time was 106 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
visitsaomiguel.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value5.8 s
15/100
25%
Value11.3 s
5/100
10%
Value1,710 ms
11/100
30%
Value0.204
61/100
15%
Value19.4 s
2/100
10%
106 ms
197 ms
583 ms
134 ms
199 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Visitsaomiguel.com, 36% (46 requests) were made to Fonts.gstatic.com and 22% (28 requests) were made to Saomiguel.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 832.4 kB (49%)
1.7 MB
849.5 kB
In fact, the total size of Visitsaomiguel.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. 75% 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. Javascripts take 619.9 kB which makes up the majority of the site volume.
Potential reduce by 46.0 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 46.0 kB or 70% of the original size.
Potential reduce by 5.2 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. Visit Sao Miguel images are well optimized though.
Potential reduce by 305.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 305.2 kB or 49% of the original size.
Potential reduce by 475.9 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. Visitsaomiguel.com needs all CSS files to be minified and compressed as it can save up to 475.9 kB or 81% of the original size.
Number of requests can be reduced by 46 (60%)
77
31
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Visit Sao Miguel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
visitsaomiguel.com
106 ms
www.saomiguel.com
197 ms
www.saomiguel.com
583 ms
analytics.js
134 ms
css
199 ms
bootstrap.min.css
174 ms
font-awesome.min.css
183 ms
owl.carousel.min.css
185 ms
animate.min.css
201 ms
revolution-slider.css
244 ms
layerslider.css
428 ms
essentials.css
526 ms
layout.css
430 ms
header-3.css
341 ms
footer-default.css
342 ms
green.css
341 ms
modernizr.min.js
217 ms
jquery.min.js
150 ms
owl.carousel.min.js
190 ms
bootstrap.min.js
152 ms
jquery.themepunch.plugins.min.js
496 ms
jquery.themepunch.revolution.min.js
742 ms
revolution_slider.js
404 ms
scripts.js
898 ms
collect
23 ms
87405989
605 ms
2gYRJUgsvi0
603 ms
pattern7.png
168 ms
saomiguelazores.png
168 ms
1x1.png
168 ms
1.jpg
168 ms
2.jpg
167 ms
3.jpg
483 ms
4.jpg
299 ms
5.jpg
299 ms
6.jpg
284 ms
7.jpg
284 ms
8.jpg
585 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff
357 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQUwaEQXjN_mQ.woff
376 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4vaVQUwaEQXjN_mQ.woff
455 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4iaVQUwaEQXjN_mQ.woff
503 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4jaVQUwaEQXjN_mQ.woff
595 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4saVQUwaEQXjN_mQ.woff
595 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQUwaEQXjN_mQ.woff
595 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVQUwaEQXjN_mQ.woff
595 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQUwaEQXjM.woff
595 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQUwaEQXjN_mQ.woff
594 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4vaVQUwaEQXjN_mQ.woff
937 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4iaVQUwaEQXjN_mQ.woff
938 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4jaVQUwaEQXjN_mQ.woff
938 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4saVQUwaEQXjN_mQ.woff
937 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVQUwaEQXjN_mQ.woff
937 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4taVQUwaEQXjN_mQ.woff
937 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQUwaEQXjM.woff
1038 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQUwaEQXjN_mQ.woff
1038 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4vaVQUwaEQXjN_mQ.woff
1037 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4iaVQUwaEQXjN_mQ.woff
1037 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4jaVQUwaEQXjN_mQ.woff
1038 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4saVQUwaEQXjN_mQ.woff
1036 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQUwaEQXjN_mQ.woff
1396 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVQUwaEQXjN_mQ.woff
1416 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQUwaEQXjM.woff
1415 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQUwaEQXjN_mQ.woff
1415 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4vaVQUwaEQXjN_mQ.woff
1393 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4iaVQUwaEQXjN_mQ.woff
1412 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4jaVQUwaEQXjN_mQ.woff
1602 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4saVQUwaEQXjN_mQ.woff
1605 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4kaVQUwaEQXjN_mQ.woff
1604 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4taVQUwaEQXjN_mQ.woff
1605 ms
fontawesome-webfont.woff
87 ms
js
880 ms
loader.gif
602 ms
bullet.png
603 ms
1.jpg
1283 ms
www-player.css
921 ms
revicons.woff
540 ms
www-embed-player.js
930 ms
base.js
1432 ms
fetch-polyfill.js
604 ms
465453423-0e9ebf810e5e33dc6884ecaadd5f318cf66a2d7fc8634513322f8da8cd56d14d-d.jpg
1169 ms
player.js
1256 ms
player.css
1094 ms
vuid.min.js
975 ms
gen_204
441 ms
common.js
371 ms
util.js
374 ms
map.js
367 ms
marker.js
365 ms
465453423-0e9ebf810e5e33dc6884ecaadd5f318cf66a2d7fc8634513322f8da8cd56d14d-d
210 ms
controls.js
76 ms
openhand_8_8.cur
754 ms
onion.js
79 ms
ad_status.js
1005 ms
ViewportInfoService.GetViewportInfo
962 ms
NAdTarfwBmmVN2jO9_ZDZXbW2JobdXK1pZJ09rC2Bcw.js
790 ms
embed.js
332 ms
google_gray.svg
381 ms
id
291 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
137 ms
KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff
138 ms
KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff
106 ms
KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff
104 ms
KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff
107 ms
KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff
106 ms
KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff
112 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
112 ms
KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff
112 ms
KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff
109 ms
KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff
111 ms
KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff
112 ms
KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff
216 ms
KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff
218 ms
AuthenticationService.Authenticate
188 ms
vt
171 ms
vt
485 ms
vt
483 ms
vt
483 ms
vt
484 ms
vt
483 ms
vt
486 ms
vt
487 ms
vt
485 ms
Create
511 ms
transparent.png
312 ms
vt
47 ms
QuotaService.RecordEvent
31 ms
vt
42 ms
visitsaomiguel.com accessibility score
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
button, link, and menuitem elements do not have accessible names.
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
<frame> or <iframe> elements do not have a title
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
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.
visitsaomiguel.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
Page has valid source maps
visitsaomiguel.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Visitsaomiguel.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Visitsaomiguel.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.
visitsaomiguel.com
Open Graph description is not detected on the main page of Visit Sao Miguel. 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: