13.3 sec in total
1.6 sec
11.6 sec
124 ms
Visit epay.163.com now to see the best up-to-date Epay 163 content for China and also check out these interesting facts you probably never knew about epay.163.com
Visit epay.163.comWe analyzed Epay.163.com page load time and found that the first response time was 1.6 sec and then it took 11.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
epay.163.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value6.7 s
8/100
25%
Value11.8 s
4/100
10%
Value140 ms
96/100
30%
Value0
100/100
15%
Value9.2 s
32/100
10%
1583 ms
1221 ms
2350 ms
2383 ms
2677 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that 11% of them (3 requests) were addressed to the original Epay.163.com, 86% (24 requests) were made to I.epay.126.net and 4% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source I.epay.126.net.
Page size can be reduced by 141.0 kB (31%)
455.2 kB
314.2 kB
In fact, the total size of Epay.163.com main page is 455.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 282.8 kB which makes up the majority of the site volume.
Potential reduce by 6.8 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. 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 6.8 kB or 66% of the original size.
Potential reduce by 10.8 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. Epay 163 images are well optimized though.
Potential reduce by 50.1 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 50.1 kB or 68% of the original size.
Potential reduce by 73.3 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. Epay.163.com needs all CSS files to be minified and compressed as it can save up to 73.3 kB or 83% of the original size.
Number of requests can be reduced by 13 (50%)
26
13
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epay 163. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
epay.163.com
1583 ms
epay.163.com
1221 ms
base.css
2350 ms
module.css
2383 ms
include.css
2677 ms
style.css
3046 ms
jquery-1.11.2.min.js
4123 ms
sea.js
3003 ms
seajs-config.js
3269 ms
login.css
4012 ms
authCode
887 ms
logo.png
860 ms
b1.jpg
3896 ms
b5.jpg
4474 ms
b6.jpg
2594 ms
b3.jpg
1323 ms
phoneBg.png
1938 ms
loading.gif
1193 ms
i1.png
2515 ms
icon4integrityV2.png
1656 ms
login.js
1964 ms
analytics.js
2851 ms
epay.js
319 ms
md5.js
643 ms
dialog.js
846 ms
autocomplete.js
2638 ms
safeCtrl.js
991 ms
collect
72 ms
epay.163.com 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.
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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
epay.163.com 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
epay.163.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
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 doesn't use legible font sizes
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epay.163.com 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 Epay.163.com 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.
epay.163.com
Open Graph description is not detected on the main page of Epay 163. 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: