Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

prettylittleliars.com

Log into Facebook

Page Load Speed

67.7 sec in total

First Response

300 ms

Resources Loaded

54.9 sec

Page Rendered

12.5 sec

prettylittleliars.com screenshot

About Website

Click here to check amazing Prettylittleliars content for United States. Otherwise, check out these important facts you probably never knew about prettylittleliars.com

Log into Facebook to start sharing and connecting with your friends, family, and people you know.

Visit prettylittleliars.com

Key Findings

We analyzed Prettylittleliars.com page load time and found that the first response time was 300 ms and then it took 67.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 10 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

prettylittleliars.com performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.1 s

86/100

10%

Network Requests Diagram

prettylittleliars.com

300 ms

1392 ms

MKXBVqUyW47.css

1070 ms

msD4y6jSjpk.css

1417 ms

OW-sD7A8PMa.css

1510 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Prettylittleliars.com, 78% (83 requests) were made to Static.xx.fbcdn.net and 13% (14 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (23.6 sec) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (27%)

Content Size

4.5 MB

After Optimization

3.3 MB

In fact, the total size of Prettylittleliars.com main page is 4.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 505.7 kB

  • Original 651.1 kB
  • After minification 651.1 kB
  • After compression 145.4 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 505.7 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 57.7 kB

  • Original 2.9 MB
  • After minification 2.8 MB

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. Prettylittleliars images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 584.6 kB

  • Original 895.5 kB
  • After minification 876.2 kB
  • After compression 310.9 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 584.6 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 93.9 kB

  • Original 113.9 kB
  • After minification 107.2 kB
  • After compression 20.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. Prettylittleliars.com needs all CSS files to be minified and compressed as it can save up to 93.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (72%)

Requests Now

92

After Optimization

26

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

Accessibility Review

prettylittleliars.com accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

prettylittleliars.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

High

Browser errors were logged to the console

SEO Factors

prettylittleliars.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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 Prettylittleliars.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 Prettylittleliars.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 Prettylittleliars. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: