Report Summary

  • 0

    Performance

  • 34

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

Page Load Speed

3 sec in total

First Response

386 ms

Resources Loaded

2.6 sec

Page Rendered

53 ms

mackendrew.org screenshot

About Website

Click here to check amazing Mackendrew content. Otherwise, check out these important facts you probably never knew about mackendrew.org

Visit mackendrew.org

Key Findings

We analyzed Mackendrew.org page load time and found that the first response time was 386 ms and then it took 2.6 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

mackendrew.org performance score

0

Network Requests Diagram

mackendrew.org

386 ms

push.js

675 ms

common.js

64 ms

tj.js

127 ms

277 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 38% of them (3 requests) were addressed to the original Mackendrew.org, 25% (2 requests) were made to Node11.aizhantj.com and 25% (2 requests) were made to Node31.aizhantj.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Node31.aizhantj.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 kB (53%)

Content Size

3.9 kB

After Optimization

1.8 kB

In fact, the total size of Mackendrew.org main page is 3.9 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 2.9 kB which makes up the majority of the site volume.

HTML Optimization

-51%

Potential reduce by 528 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 498 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 528 B or 51% of the original size.

JavaScript Optimization

-54%

Potential reduce by 1.6 kB

  • Original 2.9 kB
  • After minification 2.5 kB
  • After compression 1.3 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 1.6 kB or 54% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (57%)

Requests Now

7

After Optimization

3

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mackendrew. 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

mackendrew.org accessibility score

34

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

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

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

mackendrew.org SEO score

75

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

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mackendrew.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Mackendrew.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 Mackendrew. 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: