Access freddyoctavio.pro. Loading...

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.154

74/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

migrate-adfly.linkvertise.com

66 ms

js

42 ms

styles.a03811aa1ead3ffb.css

12 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Freddyoctavio.pro, 33% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (66 ms) relates to the external source Migrate-adfly.linkvertise.com.

Content Size

361.3 kB

After Optimization

304.4 kB

In fact, the total size of Freddyoctavio.pro main page is 361.3 kB. This result falls within a big category (top 100 000) of medium weight web pages. Only a small number of websites need less resources to load. Javascripts take 176.5 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 1.8 kB

Original 3.1 kB
After minification 3.1 kB
After compression 1.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. 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 1.8 kB or 58% of the original size.

Image Optimization

-2%

Potential reduce by 3.5 kB

Original 146.9 kB
After minification 143.4 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. Freddyoctavio images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 22.7 kB

Original 176.5 kB
After minification 176.5 kB
After compression 153.8 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 22.7 kB or 13% of the original size.

CSS Optimization

-83%

Potential reduce by 28.9 kB

Original 34.9 kB
After minification 6.0 kB
After compression 6.0 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. Freddyoctavio.pro needs all CSS files to be minified and compressed as it can save up to 28.9 kB or 83% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Page is blocked from indexing

High

robots.txt is not valid

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

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