Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

freedomshrine.com

Freedom Shrine – Freedom Shrine

Page Load Speed

1.2 sec in total

First Response

166 ms

Resources Loaded

537 ms

Page Rendered

495 ms

About Website

Click here to check amazing Freedom Shrine content. Otherwise, check out these important facts you probably never knew about freedomshrine.com

Visit freedomshrine.com

Key Findings

We analyzed Freedomshrine.com page load time and found that the first response time was 166 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

freedomshrine.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

68/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.397

25/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

freedomshrine.com

166 ms

style.min.css

89 ms

theme.min.css

105 ms

header-footer.min.css

106 ms

frontend.min.css

108 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 71% of them (36 requests) were addressed to the original Freedomshrine.com, 25% (13 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (212 ms) belongs to the original domain Freedomshrine.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.0 kB (31%)

Content Size

225.8 kB

After Optimization

156.9 kB

In fact, the total size of Freedomshrine.com main page is 225.8 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. 40% of websites need less resources to load. Javascripts take 106.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 68.1 kB

  • Original 82.7 kB
  • After minification 82.7 kB
  • After compression 14.7 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 68.1 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 171 B

  • Original 8.6 kB
  • After minification 8.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. Freedom Shrine images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 175 B

  • Original 106.7 kB
  • After minification 106.7 kB
  • After compression 106.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 531 B

  • Original 27.8 kB
  • After minification 27.8 kB
  • After compression 27.2 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. Freedomshrine.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 29 (81%)

Requests Now

36

After Optimization

7

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

Accessibility Review

freedomshrine.com accessibility score

100

Accessibility Issues

Best Practices

freedomshrine.com best practices score

83

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

Browser errors were logged to the console

SEO Factors

freedomshrine.com SEO score

78

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freedomshrine.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 Freedomshrine.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 description is not detected on the main page of Freedom Shrine. 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: