Access charliepage.com. Charlie Page

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.369

29/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

charliepage.com

109 ms

charliepage.com

217 ms

regular.css

36 ms

solid.css

48 ms

brands.css

49 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Charliepage.com, 70% (19 requests) were made to Images.leadconnectorhq.com and 15% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Images.leadconnectorhq.com.

Content Size

434.7 kB

After Optimization

65.0 kB

In fact, the total size of Charliepage.com main page is 434.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. 20% of websites need less resources to load. HTML takes 433.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 369.6 kB

Original 433.6 kB
After minification 391.2 kB
After compression 64.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 369.6 kB or 85% of the original size.

CSS Optimization

-7%

Potential reduce by 74 B

Original 1.1 kB
After minification 1.1 kB
After compression 1.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. Charliepage.com has all CSS files already compressed.

Requests Now

After Optimization

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

Open Graph data is detected on the main page of Charlie Page. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: