Report Summary

  • 0

    Performance

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

mojing.org

mojing.org - mojing Resources and Information.

Page Load Speed

3.7 sec in total

First Response

451 ms

Resources Loaded

2.9 sec

Page Rendered

325 ms

mojing.org screenshot

About Website

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

mojing.org is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, mojing.org has it all. We hope you find what ...

Visit mojing.org

Key Findings

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

Performance Metrics

mojing.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.67

8/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

www.mojing.org

451 ms

common.js

221 ms

tj.js

432 ms

jdav522.com

79 ms

hm.js

1439 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 60% of them (3 requests) were addressed to the original Mojing.org, 20% (1 request) were made to Jdav522.com and 20% (1 request) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Hm.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 kB (41%)

Content Size

2.8 kB

After Optimization

1.6 kB

In fact, the total size of Mojing.org main page is 2.8 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 1.8 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 974 B

  • Original 1.8 kB
  • After minification 1.8 kB
  • After compression 841 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. 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 974 B or 54% of the original size.

JavaScript Optimization

-16%

Potential reduce by 152 B

  • Original 941 B
  • After minification 908 B
  • After compression 789 B

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 152 B or 16% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

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

Accessibility Review

mojing.org accessibility score

45

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

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

mojing.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

mojing.org 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

    JA

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mojing.org can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mojing.org main page’s claimed encoding is gb2312. 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 Mojing. 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: