Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 69

    Best Practices

    More advanced features
    available than in
    46% of websites

  • 67

    SEO

    Google-friendlier than
    35% of websites

lonelystar.org

星空之旅|植物大战僵尸JAVASCRIPT版|JSPVZ

Page Load Speed

70.5 sec in total

First Response

19.1 sec

Resources Loaded

51 sec

Page Rendered

366 ms

lonelystar.org screenshot

About Website

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

植物大战僵尸网页版是LonelyStar个人制作的纯JavaScript植物大战僵尸小游戏,欢迎收藏JavaScript植物大战僵尸小游戏,分享js植物大战僵尸小游戏的快乐。

Visit lonelystar.org

Key Findings

We analyzed Lonelystar.org page load time and found that the first response time was 19.1 sec and then it took 51.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 31 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

lonelystar.org performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

28/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.4 s

49/100

10%

Network Requests Diagram

lonelystar.org

19087 ms

Cfunction.js

19607 ms

stat.php

1783 ms

html_bg.gif

4200 ms

GetUser.asp

1431 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 82% of them (42 requests) were addressed to the original Lonelystar.org, 4% (2 requests) were made to Blog.lonelystar.org and 2% (1 request) were made to S9.cnzz.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Lonelystar.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 42.6 kB (75%)

Content Size

56.9 kB

After Optimization

14.3 kB

In fact, the total size of Lonelystar.org main page is 56.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 a small number of websites need less resources to load. HTML takes 39.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 33.3 kB

  • Original 39.7 kB
  • After minification 18.5 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. This page needs HTML code to be minified as it can gain 21.2 kB, which is 53% 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 33.3 kB or 84% of the original size.

Image Optimization

-33%

Potential reduce by 1.6 kB

  • Original 4.7 kB
  • After minification 3.2 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. Obviously, Lonelystar needs image optimization as it can save up to 1.6 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 7.8 kB

  • Original 12.5 kB
  • After minification 12.5 kB
  • After compression 4.7 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 7.8 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (59%)

Requests Now

17

After Optimization

7

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

Accessibility Review

lonelystar.org accessibility score

56

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

lonelystar.org best practices score

69

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

lonelystar.org SEO score

67

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lonelystar.org can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Lonelystar.org 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 Lonelystar. 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: