Tools & Wizards About Us
lopesrio.com.br screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

lopesrio.com.br

Lopes Rio • Apartamentos no Rio de Janeiro

Page Load Speed

8.7 sec in total

First Response

1.9 sec

Resources Loaded

5.6 sec

Page Rendered

1.1 sec

lopesrio.com.br screenshot

About Website

Welcome to lopesrio.com.br homepage info - get ready to check Lopes Rio best content right away, or after learning these important things about lopesrio.com.br

Compra, venda ou aluguel de apartamento no Rio de Janeiro. Há 86 anos realizando o sonho dos seus clientes. Lopes, a maior imobiliária da América Latina.

Visit lopesrio.com.br

Key Findings

We analyzed Lopesrio.com.br page load time and found that the first response time was 1.9 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize Lopesrio.com.br rating and web reputation

Performance Metrics

lopesrio.com.br performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value20.7 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

lopesrio.com.br

1933 ms

bootstrap.css

2255 ms

jquery-ui.css

17 ms

style2015.css

957 ms

jquery.min.js

23 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 37% of them (34 requests) were addressed to the original Lopesrio.com.br, 43% (39 requests) were made to Patrimovel.com.br and 5% (5 requests) were made to Site2013.patrimovel.imb.br. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Patrimovel.com.br.

Page Optimization Overview & Recommendations

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

Content Size

3.1 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 203.3 kB

  • Original 236.6 kB
  • After minification 204.1 kB
  • After compression 33.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 32.5 kB, which is 14% 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 203.3 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 101.1 kB

  • Original 2.1 MB
  • After minification 2.0 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. Lopes Rio images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 358.0 kB

  • Original 479.0 kB
  • After minification 424.5 kB
  • After compression 121.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 358.0 kB or 75% of the original size.

CSS Optimization

-83%

Potential reduce by 178.5 kB

  • Original 216.2 kB
  • After minification 174.8 kB
  • After compression 37.7 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. Lopesrio.com.br needs all CSS files to be minified and compressed as it can save up to 178.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (18%)

Requests Now

83

After Optimization

68

  • Images
  • JavaScript
  • CSS

The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lopes Rio. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lopesrio.com.br

lopesrio.com.br

1933 ms

bootstrap.css

bootstrap.css

2255 ms

jquery-ui.css

jquery-ui.css

17 ms

style2015.css

style2015.css

957 ms

jquery.min.js

jquery.min.js

23 ms

bootstrap.js

bootstrap.js

988 ms

jquery-ui.js

jquery-ui.js

20 ms

WebResource.axd

WebResource.axd

923 ms

WebResource.axd

WebResource.axd

632 ms

ScriptResource.axd

ScriptResource.axd

494 ms

ScriptResource.axd

ScriptResource.axd

523 ms

chosen.css

chosen.css

659 ms

perfect-scrollbar.css

perfect-scrollbar.css

669 ms

chosen.jquery.js

chosen.jquery.js

835 ms

perfect-scrollbar.js

perfect-scrollbar.js

815 ms

css

css

26 ms

fbevents.js

fbevents.js

15 ms

logomobile.png

logomobile.png

168 ms

13940.jpg

13940.jpg

910 ms

imagemlocal2.ashx

imagemlocal2.ashx

1305 ms

imagemlocal2.ashx

imagemlocal2.ashx

1174 ms

imagemlocal2.ashx

imagemlocal2.ashx

1143 ms

imagemlocal2.ashx

imagemlocal2.ashx

1220 ms

imagemlocal2.ashx

imagemlocal2.ashx

1358 ms

imagemlocal2.ashx

imagemlocal2.ashx

1198 ms

imagemlocal2.ashx

imagemlocal2.ashx

1662 ms

imagemlocal2.ashx

imagemlocal2.ashx

1355 ms

imagemlocal2.ashx

imagemlocal2.ashx

1386 ms

imagemlocal2.ashx

imagemlocal2.ashx

1610 ms

imagemlocal2.ashx

imagemlocal2.ashx

1603 ms

imagemlocal2.ashx

imagemlocal2.ashx

1624 ms

imagemlocal2.ashx

imagemlocal2.ashx

1587 ms

imagemlocal2.ashx

imagemlocal2.ashx

1587 ms

imagemlocal2.ashx

imagemlocal2.ashx

1771 ms

imagemlocal2.ashx

imagemlocal2.ashx

1768 ms

imagemlocal2.ashx

imagemlocal2.ashx

1766 ms

imagemlocal2.ashx

imagemlocal2.ashx

1795 ms

imagemlocal2.ashx

imagemlocal2.ashx

1830 ms

imagemlocal2.ashx

imagemlocal2.ashx

1830 ms

imagemlocal2.ashx

imagemlocal2.ashx

1927 ms

imagemlocal2.ashx

imagemlocal2.ashx

1945 ms

imagemlocal2.ashx

imagemlocal2.ashx

1947 ms

imagemlocal2.ashx

imagemlocal2.ashx

1976 ms

imagemlocal2.ashx

imagemlocal2.ashx

1994 ms

imagemlocal2.ashx

imagemlocal2.ashx

1995 ms

imagemlocal2.ashx

imagemlocal2.ashx

2201 ms

imagemlocal2.ashx

imagemlocal2.ashx

2119 ms

imagemlocal2.ashx

imagemlocal2.ashx

2125 ms

imagemlocal2.ashx

imagemlocal2.ashx

2153 ms

imagemlocal2.ashx

imagemlocal2.ashx

2163 ms

imagemlocal2.ashx

imagemlocal2.ashx

2169 ms

imagemlocal2.ashx

imagemlocal2.ashx

2297 ms

imagemlocal2.ashx

imagemlocal2.ashx

2298 ms

imagemlocal2.ashx

imagemlocal2.ashx

2332 ms

imagemlocal2.ashx

imagemlocal2.ashx

2334 ms

logo2015.png

logo2015.png

170 ms

mobilechat.png

mobilechat.png

156 ms

mobiletel.png

mobiletel.png

170 ms

captcha.png

captcha.png

170 ms

icochatFP.png

icochatFP.png

317 ms

icoligueFT.png

icoligueFT.png

311 ms

icomailFT.png

icomailFT.png

304 ms

icochatFT.png

icochatFT.png

327 ms

17445.jpg

17445.jpg

1047 ms

130 ms

poptime.png

poptime.png

650 ms

faleconosco.png

faleconosco.png

327 ms

icochat.png

icochat.png

447 ms

liguenos.png

liguenos.png

458 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

29 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

31 ms

4cKlrioa77J2iqTqBgkRWg.ttf

4cKlrioa77J2iqTqBgkRWg.ttf

31 ms

top.png

top.png

407 ms

17871.jpg

17871.jpg

1789 ms

17870.jpg

17870.jpg

2066 ms

17869.jpg

17869.jpg

2247 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

374 ms

bgrodapeparallax.png

bgrodapeparallax.png

704 ms

icotwitter.png

icotwitter.png

481 ms

icofacebook.png

icofacebook.png

506 ms

icoyoutube.png

icoyoutube.png

493 ms

icolinkedin.png

icolinkedin.png

506 ms

happyfamily.png

happyfamily.png

1138 ms

analytics.js

analytics.js

9 ms

collect

collect

13 ms

collect

collect

56 ms

ga-audiences

ga-audiences

44 ms

glyphicons-halflings-regular.ttf

glyphicons-halflings-regular.ttf

805 ms

imagemlocal2.ashx

imagemlocal2.ashx

1197 ms

imagemlocal2.ashx

imagemlocal2.ashx

1193 ms

imagemlocal2.ashx

imagemlocal2.ashx

1285 ms

Accessibility Review

lopesrio.com.br accessibility score

75

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

[role]s do not have all required [aria-*] attributes

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

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

lopesrio.com.br best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

lopesrio.com.br SEO score

90

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lopesrio.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lopesrio.com.br 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

lopesrio.com.br

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