Tools & Wizards About Us
visitsaomiguel.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

visitsaomiguel.com

São Miguel - Visit São Miguel Island in the Azores Portugal

Page Load Speed

3 sec in total

First Response

32 ms

Resources Loaded

2.1 sec

Page Rendered

887 ms

visitsaomiguel.com screenshot

About Website

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.com

Key Findings

We analyzed Visitsaomiguel.com page load time and found that the first response time was 32 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

visitsaomiguel.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value2,700 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.204

61/100

15%

TTI (Time to Interactive)

Value22.3 s

1/100

10%

Network Requests Diagram

visitsaomiguel.com

32 ms

www.saomiguel.com

209 ms

www.saomiguel.com

368 ms

js

83 ms

css

63 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Visitsaomiguel.com, 47% (28 requests) were made to Saomiguel.com and 10% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (776 ms) relates to the external source Saomiguel.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 466.7 kB (38%)

Content Size

1.2 MB

After Optimization

767.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Visitsaomiguel.com main page is 1.2 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. Javascripts take 635.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 31.6 kB

  • Original 43.9 kB
  • After minification 38.7 kB
  • After compression 12.3 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 5.2 kB, which is 12% 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 31.6 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 4.4 kB

  • Original 297.7 kB
  • After minification 293.4 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.

JavaScript Optimization

-42%

Potential reduce by 264.9 kB

  • Original 635.5 kB
  • After minification 608.0 kB
  • After compression 370.6 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 264.9 kB or 42% of the original size.

CSS Optimization

-65%

Potential reduce by 165.8 kB

  • Original 257.0 kB
  • After minification 213.3 kB
  • After compression 91.2 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 165.8 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (57%)

Requests Now

47

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 47 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 16 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

visitsaomiguel.com

visitsaomiguel.com

32 ms

www.saomiguel.com

www.saomiguel.com

209 ms

www.saomiguel.com

www.saomiguel.com

368 ms

js

js

83 ms

css

css

63 ms

bootstrap.min.css

bootstrap.min.css

56 ms

font-awesome.min.css

font-awesome.min.css

71 ms

owl.carousel.min.css

owl.carousel.min.css

52 ms

animate.min.css

animate.min.css

49 ms

revolution-slider.css

revolution-slider.css

174 ms

layerslider.css

layerslider.css

260 ms

essentials.css

essentials.css

434 ms

layout.css

layout.css

349 ms

header-3.css

header-3.css

264 ms

footer-default.css

footer-default.css

272 ms

green.css

green.css

274 ms

modernizr.min.js

modernizr.min.js

50 ms

jquery.min.js

jquery.min.js

40 ms

owl.carousel.min.js

owl.carousel.min.js

49 ms

bootstrap.min.js

bootstrap.min.js

73 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

431 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

539 ms

revolution_slider.js

revolution_slider.js

359 ms

scripts.js

scripts.js

776 ms

87405989

87405989

188 ms

2gYRJUgsvi0

2gYRJUgsvi0

139 ms

pattern7.png

pattern7.png

89 ms

saomiguelazores.png

saomiguelazores.png

93 ms

1x1.png

1x1.png

89 ms

1.jpg

1.jpg

89 ms

2.jpg

2.jpg

188 ms

3.jpg

3.jpg

366 ms

4.jpg

4.jpg

314 ms

5.jpg

5.jpg

313 ms

6.jpg

6.jpg

365 ms

7.jpg

7.jpg

481 ms

8.jpg

8.jpg

482 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

65 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

76 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

87 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

87 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

54 ms

www-player.css

www-player.css

6 ms

www-embed-player.js

www-embed-player.js

24 ms

base.js

base.js

50 ms

ad_status.js

ad_status.js

209 ms

js

js

313 ms

loader.gif

loader.gif

267 ms

bullet.png

bullet.png

268 ms

1.jpg

1.jpg

642 ms

G9IHigwxVH3Mn3WnChzJeeVNQhz-kZ0Q5G-GviBI-tI.js

G9IHigwxVH3Mn3WnChzJeeVNQhz-kZ0Q5G-GviBI-tI.js

107 ms

embed.js

embed.js

31 ms

revicons.woff

revicons.woff

163 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

30 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

41 ms

api.js

api.js

24 ms

Create

Create

125 ms

id

id

26 ms

GenerateIT

GenerateIT

14 ms

Accessibility Review

visitsaomiguel.com accessibility score

80

Accessibility Issues

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

High

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

visitsaomiguel.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

visitsaomiguel.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: