Tools & Wizards About Us
loborges.com screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

loborges.com

Lô Borges

Page Load Speed

2.5 sec in total

First Response

301 ms

Resources Loaded

2 sec

Page Rendered

149 ms

loborges.com screenshot

About Website

Click here to check amazing Lo Borges content. Otherwise, check out these important facts you probably never knew about loborges.com

Visit loborges.com

Key Findings

We analyzed Loborges.com page load time and found that the first response time was 301 ms and then it took 2.2 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

loborges.com performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

loborges.com

301 ms

blog

530 ms

264 ms

style-new.css

132 ms

css

18 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 83% of them (10 requests) were addressed to the original Loborges.com, 8% (1 request) were made to Fonts.googleapis.com and 8% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (647 ms) belongs to the original domain Loborges.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.1 kB (2%)

Content Size

215.7 kB

After Optimization

210.5 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Loborges.com main page is 215.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. 15% of websites need less resources to load. Images take 205.6 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 3.2 kB

  • Original 4.4 kB
  • After minification 3.9 kB
  • After compression 1.2 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 574 B, which is 13% 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 3.2 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 25 B

  • Original 205.6 kB
  • After minification 205.6 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. Lo Borges images are well optimized though.

CSS Optimization

-34%

Potential reduce by 1.9 kB

  • Original 5.6 kB
  • After minification 5.6 kB
  • After compression 3.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. Loborges.com needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 34% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

  • Images
  • CSS

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lo Borges. According to our analytics all requests are already optimized.

Network Requests Diagram

loborges.com

loborges.com

301 ms

blog

blog

530 ms

264 ms

style-new.css

style-new.css

132 ms

css

css

18 ms

jquery.js

jquery.js

261 ms

background-lo-borges.jpg

background-lo-borges.jpg

389 ms

logo-lo-borges.gif

logo-lo-borges.gif

131 ms

facebook.gif

facebook.gif

259 ms

horizonte-vertical.jpg

horizonte-vertical.jpg

260 ms

foto-estrada.jpg

foto-estrada.jpg

647 ms

3y9I6aknfjLm_3lMKjiMgmUUYBs04aUXNxt9gW2LIftoqNWZd2GP.ttf

3y9I6aknfjLm_3lMKjiMgmUUYBs04aUXNxt9gW2LIftoqNWZd2GP.ttf

9 ms

Accessibility Review

loborges.com accessibility score

100

Accessibility Issues

Best Practices

loborges.com 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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

loborges.com SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    PT

  • Encoding

    UTF-8

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

loborges.com

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