Tools & Wizards About Us
vamosparaorlando.com.br screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

vamosparaorlando.com.br

Vamos para Orlando ! O guia mais completo de Orlando e região. Informações, mapas, hotel, hoteis, aluguel de carros e autos, restaurantes, lojas, parq...

Page Load Speed

3.1 sec in total

First Response

978 ms

Resources Loaded

2 sec

Page Rendered

138 ms

vamosparaorlando.com.br screenshot

About Website

Click here to check amazing Vamos Para Orlando content. Otherwise, check out these important facts you probably never knew about vamosparaorlando.com.br

Visit vamosparaorlando.com.br

Key Findings

We analyzed Vamosparaorlando.com.br page load time and found that the first response time was 978 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.

Performance Metrics

vamosparaorlando.com.br performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value3.5 s

89/100

10%

TBT (Total Blocking Time)

Value1,070 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

vamosparaorlando.com.br

978 ms

analytics.js

24 ms

adsbygoogle.js

21 ms

logo_vamosparaorlando_2011.gif

770 ms

ca-pub-8131956300514877.js

92 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 22% of them (8 requests) were addressed to the original Vamosparaorlando.com.br, 16% (6 requests) were made to Pagead2.googlesyndication.com and 14% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (985 ms) belongs to the original domain Vamosparaorlando.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.9 kB (33%)

Content Size

241.7 kB

After Optimization

161.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Vamosparaorlando.com.br main page is 241.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 155.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 14.1 kB

  • Original 18.2 kB
  • After minification 16.4 kB
  • After compression 4.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. 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 14.1 kB or 77% of the original size.

Image Optimization

-25%

Potential reduce by 17.3 kB

  • Original 68.6 kB
  • After minification 51.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. Obviously, Vamos Para Orlando needs image optimization as it can save up to 17.3 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-31%

Potential reduce by 48.5 kB

  • Original 155.0 kB
  • After minification 153.0 kB
  • After compression 106.5 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 48.5 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (59%)

Requests Now

34

After Optimization

14

  • AJAX
  • Images
  • JavaScript

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vamos Para Orlando. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

vamosparaorlando.com.br

vamosparaorlando.com.br

978 ms

analytics.js

analytics.js

24 ms

adsbygoogle.js

adsbygoogle.js

21 ms

logo_vamosparaorlando_2011.gif

logo_vamosparaorlando_2011.gif

770 ms

ca-pub-8131956300514877.js

ca-pub-8131956300514877.js

92 ms

zrt_lookup.html

zrt_lookup.html

92 ms

show_ads_impl.js

show_ads_impl.js

90 ms

collect

collect

29 ms

ads

ads

374 ms

osd.js

osd.js

18 ms

icon_facebook.GIF

icon_facebook.GIF

148 ms

icon_twitter.gif

icon_twitter.gif

495 ms

icon_youtube.gif

icon_youtube.gif

494 ms

logo_instag.gif

logo_instag.gif

489 ms

vera_09.jpg

vera_09.jpg

985 ms

counter.js

counter.js

14 ms

show_ads.js

show_ads.js

9 ms

Wizarding-.gif

Wizarding-.gif

492 ms

counter.asp

counter.asp

6 ms

analytics.js

analytics.js

157 ms

mpp.vindicosuite.com

mpp.vindicosuite.com

44 ms

meter.asp

meter.asp

38 ms

ads

ads

294 ms

meter.asp

meter.asp

24 ms

0

0

77 ms

46 ms

blank.gif

blank.gif

79 ms

0

0

14 ms

12031235706538053787

12031235706538053787

93 ms

abg.js

abg.js

105 ms

m_js_controller.js

m_js_controller.js

109 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

216 ms

s

s

101 ms

x_button_blue2.png

x_button_blue2.png

98 ms

favicon

favicon

217 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

28 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

11 ms

Accessibility Review

vamosparaorlando.com.br accessibility score

63

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

[aria-*] attributes do not match their roles

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

vamosparaorlando.com.br best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

vamosparaorlando.com.br SEO score

58

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vamosparaorlando.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Vamosparaorlando.com.br main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

vamosparaorlando.com.br

Open Graph description is not detected on the main page of Vamos Para Orlando. 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: