15.5 sec in total
1.3 sec
14.1 sec
199 ms
Welcome to hexa.us homepage info - get ready to check Hexa best content for China right away, or after learning these important things about hexa.us
技术向与资源向LOL英雄联盟网站
Visit hexa.usWe analyzed Hexa.us page load time and found that the first response time was 1.3 sec and then it took 14.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
hexa.us performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value4.3 s
43/100
25%
Value3.0 s
94/100
10%
Value200 ms
90/100
30%
Value0.029
100/100
15%
Value7.3 s
49/100
10%
1252 ms
231 ms
2055 ms
6149 ms
1945 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 13% of them (6 requests) were addressed to the original Hexa.us, 24% (11 requests) were made to Static1.hexa.us and 15% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (6.6 sec) relates to the external source Cdn.staticfile.org.
Page size can be reduced by 680.8 kB (67%)
1.0 MB
336.2 kB
In fact, the total size of Hexa.us main page is 1.0 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. 45% of websites need less resources to load. Javascripts take 808.6 kB which makes up the majority of the site volume.
Potential reduce by 19.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 3.1 kB, which is 13% 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 19.3 kB or 80% of the original size.
Potential reduce by 211 B
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. Hexa images are well optimized though.
Potential reduce by 506.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 506.7 kB or 63% of the original size.
Potential reduce by 154.6 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. Hexa.us needs all CSS files to be minified and compressed as it can save up to 154.6 kB or 86% of the original size.
Number of requests can be reduced by 31 (74%)
42
11
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hexa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
hexa.us
1252 ms
lightbox.min.css
231 ms
bootstrap.css
2055 ms
font-awesome.min.css
6149 ms
red.css
1945 ms
core.css
1949 ms
zanblog.js
1953 ms
jquery.min.js
6574 ms
bootstrap.js
1954 ms
jquery.icheck.js
1950 ms
jquery.validate.min.js
5886 ms
jquery.lazyload.min.js
5922 ms
zanblog.js
2174 ms
custom.js
2180 ms
jquery-migrate.min.js
439 ms
adsbygoogle.js
7 ms
jquery.infinitescroll.js
440 ms
wp-lightbox-2.min.js
440 ms
wp-embed.min.js
451 ms
bg.jpg
337 ms
logo.png
245 ms
fontawesome-webfont.woff
1709 ms
ca-pub-8505625591903348.js
52 ms
zrt_lookup.html
40 ms
show_ads_impl.js
60 ms
stat.php
1041 ms
ads
314 ms
osd.js
12 ms
ads
274 ms
m_js_controller.js
31 ms
abg.js
48 ms
favicon
1849 ms
favicon
50 ms
googlelogo_color_112x36dp.png
62 ms
nessie_icon_tiamat_white.png
32 ms
s
31 ms
x_button_blue2.png
15 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
3 ms
stat.htm
157 ms
core.php
1411 ms
activeview
17 ms
9.gif
2361 ms
pic.gif
1110 ms
red.png
234 ms
activeview
15 ms
app.gif
1392 ms
hexa.us accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
Links do not have a discernible name
hexa.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hexa.us SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hexa.us can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that Hexa.us 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.
hexa.us
Open Graph description is not detected on the main page of Hexa. 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: