Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

mmy.moe

Forums - 萌命缘 10th - MMYMOE

Page Load Speed

7.2 sec in total

First Response

661 ms

Resources Loaded

6 sec

Page Rendered

546 ms

mmy.moe screenshot

About Website

Welcome to mmy.moe homepage info - get ready to check Mmy best content for Japan right away, or after learning these important things about mmy.moe

Visit mmy.moe

Key Findings

We analyzed Mmy.moe page load time and found that the first response time was 661 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

mmy.moe performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

87/100

25%

SI (Speed Index)

Value2.6 s

97/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

mmy.moe

661 ms

www.mmy.moe

1616 ms

uaredirect.js

481 ms

style.css

171 ms

prettyPhoto.css

325 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 96% of them (26 requests) were addressed to the original Mmy.moe, 4% (1 request) were made to Siteapp.baidu.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Mmy.moe.

Page Optimization Overview & Recommendations

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

Content Size

13.6 MB

After Optimization

12.9 MB

In fact, the total size of Mmy.moe main page is 13.6 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. 40% of websites need less resources to load. Images take 13.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 15.3 kB

  • Original 17.8 kB
  • After minification 8.9 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 8.9 kB, which is 50% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 15.3 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 517.7 kB

  • Original 13.3 MB
  • After minification 12.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. Mmy images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 112.6 kB

  • Original 166.2 kB
  • After minification 166.2 kB
  • After compression 53.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 112.6 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 46.3 kB

  • Original 55.0 kB
  • After minification 54.5 kB
  • After compression 8.8 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. Mmy.moe needs all CSS files to be minified and compressed as it can save up to 46.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (12%)

Requests Now

25

After Optimization

22

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

Accessibility Review

mmy.moe accessibility score

68

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

Document doesn't have a <title> element

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

mmy.moe 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

SEO Factors

mmy.moe SEO score

55

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mmy.moe can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Mmy.moe 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 Mmy. 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: