Tools & Wizards About Us
movile.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

movile.com

Movile | We Accelerate Tech Companies and People

Page Load Speed

20.7 sec in total

First Response

5.8 sec

Resources Loaded

14.6 sec

Page Rendered

207 ms

movile.com screenshot

About Website

Visit movile.com now to see the best up-to-date Movile content for Brazil and also check out these interesting facts you probably never knew about movile.com

Somos uma investidora brasileira que realiza aportes de longo prazo em empresas de tecnologia na América Latina.

Visit movile.com

Key Findings

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

Performance Metrics

movile.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value3,330 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

5823 ms

jquery.min.js

65 ms

wp.css

427 ms

style.css

407 ms

jquery.fancybox.css

426 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 93% of them (71 requests) were addressed to the original Movile.com, 3% (2 requests) were made to Ajax.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Movile.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 896.5 kB (27%)

Content Size

3.3 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Movile.com main page is 3.3 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. 50% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 416.5 kB

  • Original 533.0 kB
  • After minification 528.1 kB
  • After compression 116.5 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 416.5 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 135.3 kB

  • Original 2.3 MB
  • After minification 2.2 MB

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. Movile images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 241.7 kB

  • Original 387.8 kB
  • After minification 368.5 kB
  • After compression 146.1 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 241.7 kB or 62% of the original size.

CSS Optimization

-87%

Potential reduce by 103.1 kB

  • Original 118.3 kB
  • After minification 83.6 kB
  • After compression 15.1 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. Movile.com needs all CSS files to be minified and compressed as it can save up to 103.1 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (24%)

Requests Now

71

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

5823 ms

jquery.min.js

jquery.min.js

65 ms

wp.css

wp.css

427 ms

style.css

style.css

407 ms

jquery.fancybox.css

jquery.fancybox.css

426 ms

ProdutosParaVoce.css

ProdutosParaVoce.css

428 ms

ProdutosParaEmpresas.css

ProdutosParaEmpresas.css

428 ms

jquery.min.js

jquery.min.js

85 ms

jquery.responsiveTabs.min.js

jquery.responsiveTabs.min.js

414 ms

comment-reply.min.js

comment-reply.min.js

821 ms

wp-embed.min.js

wp-embed.min.js

839 ms

unslider.min.js

unslider.min.js

849 ms

jquery.fancybox.js

jquery.fancybox.js

1144 ms

javascript.js

javascript.js

854 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

535 ms

analytics.js

analytics.js

55 ms

822 ms

f_hover.png

f_hover.png

1610 ms

i_hover.png

i_hover.png

1505 ms

r_hover.png

r_hover.png

1494 ms

m_hover.png

m_hover.png

1816 ms

e_hover.png

e_hover.png

1779 ms

gente_hover.png

gente_hover.png

2021 ms

case1_thumbnail_selected.png

case1_thumbnail_selected.png

2472 ms

case2_thumbnail_selected.png

case2_thumbnail_selected.png

1933 ms

case3_thumbnail_selected.png

case3_thumbnail_selected.png

2326 ms

case4_thumbnail_selected.png

case4_thumbnail_selected.png

2606 ms

case5_thumbnail_selected.png

case5_thumbnail_selected.png

2780 ms

case6_thumbnail_selected.png

case6_thumbnail_selected.png

2788 ms

movile.png

movile.png

2461 ms

menu640.png

menu640.png

2744 ms

seleciona.png

seleciona.png

2880 ms

unitedStates.png

unitedStates.png

2887 ms

iconB2C_PlayKids.png

iconB2C_PlayKids.png

3147 ms

iconB2C_iFood.png

iconB2C_iFood.png

3287 ms

iconB2C_Apontador.png

iconB2C_Apontador.png

3334 ms

iconB2B_rapiddo.png

iconB2B_rapiddo.png

3337 ms

iconB2C_Superplayer.png

iconB2C_Superplayer.png

3437 ms

iconB2C_Cheftime.png

iconB2C_Cheftime.png

3430 ms

iconB2B_MessagingRet.png

iconB2B_MessagingRet.png

3562 ms

iconB2C_Cinepapaya.png

iconB2C_Cinepapaya.png

3708 ms

underline.png

underline.png

3744 ms

techCrunch_hover.png

techCrunch_hover.png

3749 ms

tnw_hover.png

tnw_hover.png

3847 ms

exame_hover.png

exame_hover.png

3849 ms

info_hover.png

info_hover.png

3959 ms

collect

collect

13 ms

collect

collect

53 ms

Helvetica%20Neue%20UltraLight.woff

Helvetica%20Neue%20UltraLight.woff

4321 ms

Helvetica%20Neue%20Light.woff

Helvetica%20Neue%20Light.woff

4207 ms

Helvetica%20Neue.woff

Helvetica%20Neue.woff

4622 ms

dinheiro_hover.png

dinheiro_hover.png

3877 ms

forbes_hover.png

forbes_hover.png

3753 ms

gigaom_hover1.png

gigaom_hover1.png

3611 ms

style.css

style.css

3885 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

3625 ms

projekktor-1.3.09.min.js

projekktor-1.3.09.min.js

3909 ms

custom.js

custom.js

3397 ms

allThings_hover.png

allThings_hover.png

3319 ms

idgnow_hover.png

idgnow_hover.png

3302 ms

estadao_hover.png

estadao_hover.png

3547 ms

infoweek_hover.png

infoweek_hover.png

3458 ms

readWriteWeb_hover.png

readWriteWeb_hover.png

3198 ms

valorEconomico_hover.png

valorEconomico_hover.png

3075 ms

folhaDeSaoPaulo_hover.png

folhaDeSaoPaulo_hover.png

3067 ms

vb_hover.png

vb_hover.png

3219 ms

nyt_hover.png

nyt_hover.png

3268 ms

wsj_hover.png

wsj_hover.png

3459 ms

melhorEmpresaParaTrabalhar3.png

melhorEmpresaParaTrabalhar3.png

3276 ms

linkedin-icon.png

linkedin-icon.png

3063 ms

facebook-icon.png

facebook-icon.png

3059 ms

twitter-icon.png

twitter-icon.png

3092 ms

pinterest-icon.png

pinterest-icon.png

3072 ms

lime.png

lime.png

3024 ms

start.png

start.png

974 ms

bg.jpg

bg.jpg

1718 ms

Accessibility Review

movile.com accessibility score

75

Accessibility Issues

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

High

Image elements do not have [alt] attributes

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.

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 IDs are not unique

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

movile.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

movile.com SEO score

84

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

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Movile.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Movile.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

movile.com

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