Tools & Wizards About Us
romera.com.br screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

romera.com.br

Romera - |

Page Load Speed

5.6 sec in total

First Response

1.2 sec

Resources Loaded

4.3 sec

Page Rendered

141 ms

romera.com.br screenshot

About Website

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

A Romera é uma rede de lojas sediada em Arapongas/PR. Com mais de 150 lojas, está presente em sete estados do Brasil.

Visit romera.com.br

Key Findings

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

Performance Metrics

romera.com.br performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.142

78/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

www.romera.com.br

1165 ms

style.css

464 ms

jquery.fancybox.css

286 ms

jquery-1.11.1.min.js

720 ms

jquery-ui.js

5 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 77% of them (24 requests) were addressed to the original Romera.com.br, 6% (2 requests) were made to Googletagmanager.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Romera.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 311.3 kB (25%)

Content Size

1.2 MB

After Optimization

936.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Romera.com.br 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. 30% of websites need less resources to load. Images take 871.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 19.6 kB

  • Original 25.6 kB
  • After minification 23.9 kB
  • After compression 6.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 19.6 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 42.0 kB

  • Original 871.8 kB
  • After minification 829.8 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. Romera images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 184.7 kB

  • Original 273.1 kB
  • After minification 266.0 kB
  • After compression 88.3 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 184.7 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 64.9 kB

  • Original 77.0 kB
  • After minification 70.5 kB
  • After compression 12.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. Romera.com.br needs all CSS files to be minified and compressed as it can save up to 64.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (40%)

Requests Now

25

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Romera. 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

www.romera.com.br

www.romera.com.br

1165 ms

style.css

style.css

464 ms

jquery.fancybox.css

jquery.fancybox.css

286 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

720 ms

jquery-ui.js

jquery-ui.js

5 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

803 ms

jquery.customSelect.min.js

jquery.customSelect.min.js

1471 ms

jquery.meio.mask.min.js

jquery.meio.mask.min.js

1630 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

568 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

609 ms

base.js

base.js

710 ms

stylesheet.css

stylesheet.css

291 ms

Banner-Romera7.png

Banner-Romera7.png

1015 ms

Banner-Romera-2.jpg

Banner-Romera-2.jpg

292 ms

gtm.js

gtm.js

46 ms

sprite-tema-main-gray.png

sprite-tema-main-gray.png

145 ms

instagram.png

instagram.png

153 ms

linkedin.png

linkedin.png

289 ms

youtube.png

youtube.png

302 ms

plus.png

plus.png

428 ms

ball-banner-h.png

ball-banner-h.png

1146 ms

ball-banner.png

ball-banner.png

1403 ms

bg-encontre.jpg

bg-encontre.jpg

578 ms

gtm.js

gtm.js

37 ms

aller_rg-webfont.woff

aller_rg-webfont.woff

687 ms

base.js

base.js

313 ms

analytics.js

analytics.js

14 ms

piwik.js

piwik.js

164 ms

sdk.js

sdk.js

17 ms

collect

collect

42 ms

sdk.js

sdk.js

8 ms

Accessibility Review

romera.com.br accessibility score

95

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

Links do not have a discernible name

Best Practices

romera.com.br best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

romera.com.br SEO score

69

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

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

romera.com.br

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