Report Summary

  • 77

    Performance

    Renders faster than
    85% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

roguedecker.com

Magic: the Gathering News and Tools | RogueDecker.com

Page Load Speed

4.2 sec in total

First Response

183 ms

Resources Loaded

3.4 sec

Page Rendered

565 ms

roguedecker.com screenshot

About Website

Welcome to roguedecker.com homepage info - get ready to check Rogue Decker best content right away, or after learning these important things about roguedecker.com

Magic: the Gathering news and tools. Always working on new features to improve your Magic: the Gathering game.

Visit roguedecker.com

Key Findings

We analyzed Roguedecker.com page load time and found that the first response time was 183 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

roguedecker.com performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

roguedecker.com

183 ms

roguedecker.com

253 ms

basic.php

67 ms

custom.php

135 ms

scripts.js

173 ms

Our browser made a total of 168 requests to load all elements on the main page. We found that 99% of them (167 requests) were addressed to the original Roguedecker.com, 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Roguedecker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.6 MB (7%)

Content Size

64.3 MB

After Optimization

59.7 MB

In fact, the total size of Roguedecker.com main page is 64.3 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. 60% of websites need less resources to load. Images take 64.2 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 20.9 kB

  • Original 27.4 kB
  • After minification 27.3 kB
  • After compression 6.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 20.9 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 4.6 MB

  • Original 64.2 MB
  • After minification 59.6 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. Rogue Decker images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 42 B

  • Original 30.7 kB
  • After minification 30.7 kB
  • After compression 30.6 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

We found no issues to fix!

Requests Now

164

After Optimization

164

The browser has sent 164 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rogue Decker. According to our analytics all requests are already optimized.

Accessibility Review

roguedecker.com accessibility score

95

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.

Best Practices

roguedecker.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roguedecker.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 Roguedecker.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 Rogue Decker. 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: