Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

elvis.org

☞Elvis The King

Page Load Speed

2.8 sec in total

First Response

105 ms

Resources Loaded

2.1 sec

Page Rendered

539 ms

elvis.org screenshot

About Website

Visit elvis.org now to see the best up-to-date Elvis content and also check out these interesting facts you probably never knew about elvis.org

Elvis The King - Everything About Elvis - A lot of downloads - The Elvis Presley Story - The Elvis Trading Cards - Interviews - Concert Tickets - Forums - Chat

Visit elvis.org

Key Findings

We analyzed Elvis.org page load time and found that the first response time was 105 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

elvis.org performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

elvis.org

105 ms

www.elvis.net

287 ms

elviscar.gif

179 ms

elvis.gif

149 ms

jail.gif

70 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Elvis.org, 50% (21 requests) were made to Elvis.net and 17% (7 requests) were made to Images.bravenet.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Churros.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 36.5 kB (5%)

Content Size

716.7 kB

After Optimization

680.1 kB

In fact, the total size of Elvis.org main page is 716.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. 25% of websites need less resources to load. Images take 677.9 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 17.1 kB

  • Original 24.2 kB
  • After minification 23.7 kB
  • After compression 7.1 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 17.1 kB or 71% of the original size.

Image Optimization

-3%

Potential reduce by 19.3 kB

  • Original 677.9 kB
  • After minification 658.6 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. Elvis images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 125 B

  • Original 14.6 kB
  • After minification 14.5 kB
  • After compression 14.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.

Requests Breakdown

Number of requests can be reduced by 9 (23%)

Requests Now

39

After Optimization

30

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elvis. 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 JavaScripts and as a result speed up the page load time.

Accessibility Review

elvis.org accessibility score

33

Accessibility Issues

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

elvis.org best practices score

58

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

elvis.org SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elvis.org 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), while the claimed language is English. Our system also found out that Elvis.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Elvis. 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: