70.5 sec in total
19.1 sec
51 sec
366 ms
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.orgWe 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.
lonelystar.org performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value5.0 s
28/100
25%
Value6.3 s
42/100
10%
Value610 ms
49/100
30%
Value0
100/100
15%
Value7.4 s
49/100
10%
19087 ms
19607 ms
1783 ms
4200 ms
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 size can be reduced by 42.6 kB (75%)
56.9 kB
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.
Potential reduce by 33.3 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.
Potential reduce by 1.6 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.
Potential reduce by 7.8 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.
Number of requests can be reduced by 10 (59%)
17
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.
lonelystar.org
19087 ms
Cfunction.js
19607 ms
stat.php
1783 ms
html_bg.gif
4200 ms
GetUser.asp
1431 ms
popclub-linklogo.gif
1976 ms
x453.gif
15165 ms
logo120_60.png
1650 ms
body.jpg
10601 ms
sod1row.png
12798 ms
SunFlower1.gif
9662 ms
Peashooter.gif
6931 ms
SunShroom2.gif
3951 ms
1.gif
19994 ms
Sun.gif
19995 ms
12581.jpg
16625 ms
TZH_YXZX3.jpg
17864 ms
20929.jpg
15773 ms
gameTontie.jpg
19994 ms
41688.jpg
19995 ms
42917.jpg
19995 ms
10101.jpg
19996 ms
62460.jpg
19996 ms
b_google.gif
19996 ms
b_ie.gif
19996 ms
b_firefox.gif
19996 ms
b_safari.gif
19997 ms
b_opera.gif
19996 ms
b_qq.gif
19996 ms
b_max.gif
19996 ms
b_sougou.gif
19996 ms
b_360.gif
19996 ms
b_theworld.gif
19995 ms
a5logo.png
19995 ms
websiteui.gif
7537 ms
stat.htm
260 ms
core.php
872 ms
9.gif
826 ms
header.jpg
20101 ms
nav_bg.jpg
20102 ms
main_bg.jpg
20101 ms
c_on.jpg
20100 ms
ipt_03.jpg
20101 ms
ipt_01.jpg
20100 ms
undefined
20046 ms
info_bg.jpg
19975 ms
info_ico.jpg
19976 ms
game_bg.png
19976 ms
app.gif
840 ms
link_bg.jpg
20043 ms
footer_BG.jpg
20065 ms
lonelystar.org accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
<html> element does not have a [lang] attribute
lonelystar.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
lonelystar.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
ZH
N/A
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.
lonelystar.org
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: