Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

legacy180.com

Loading...

Page Load Speed

305 ms in total

First Response

151 ms

Resources Loaded

154 ms

Page Rendered

0 ms

About Website

Visit legacy180.com now to see the best up-to-date Legacy 180 content and also check out these interesting facts you probably never knew about legacy180.com

Visit legacy180.com

Key Findings

We analyzed Legacy180.com page load time and found that the first response time was 151 ms and then it took 154 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

legacy180.com performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.076

95/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

legacy180.com

151 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Legacy180.com and no external sources were called. The less responsive or slowest element that took the longest time to load (151 ms) belongs to the original domain Legacy180.com.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

legacy180.com accessibility score

78

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

SEO Factors

legacy180.com SEO score

100

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Legacy180.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Legacy180.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 Legacy 180. 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: