Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

frum.com.br

Indústria Metalúrgica Frum

Page Load Speed

3 sec in total

First Response

258 ms

Resources Loaded

2.7 sec

Page Rendered

59 ms

frum.com.br screenshot

About Website

Click here to check amazing Frum content. Otherwise, check out these important facts you probably never knew about frum.com.br

Visit frum.com.br

Key Findings

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

Performance Metrics

frum.com.br performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

www.frum.com.br

258 ms

minified.js

37 ms

focus-within-polyfill.js

34 ms

polyfill.min.js

1016 ms

thunderbolt-commons.40a6e213.bundle.min.js

61 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Frum.com.br, 42% (24 requests) were made to Static.wixstatic.com and 30% (17 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 417.9 kB (41%)

Content Size

1.0 MB

After Optimization

604.3 kB

In fact, the total size of Frum.com.br main page is 1.0 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. HTML takes 410.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 315.6 kB

  • Original 410.8 kB
  • After minification 409.0 kB
  • After compression 95.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 315.6 kB or 77% of the original size.

Image Optimization

-17%

Potential reduce by 54.2 kB

  • Original 313.6 kB
  • After minification 259.5 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, Frum needs image optimization as it can save up to 54.2 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 48.1 kB

  • Original 297.8 kB
  • After minification 297.8 kB
  • After compression 249.7 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.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (28%)

Requests Now

40

After Optimization

29

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

Accessibility Review

frum.com.br accessibility score

100

Accessibility Issues

Best Practices

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

frum.com.br SEO score

88

Search Engine Optimization Advices

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

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frum.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 Frum.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

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