13.3 sec in total
1.6 sec
11.4 sec
311 ms
Visit axure.org now to see the best up-to-date Axure content for China and also check out these interesting facts you probably never knew about axure.org
Axure中文社区,创办于2007年12月11日,超过15万注册用户,Axure及原型设计作品的分享平台,支持rp文件在线生成,提供有产品经理和交互设计师的培训。
Visit axure.orgWe analyzed Axure.org 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.
axure.org performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value2.6 s
87/100
25%
Value4.8 s
67/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.1 s
99/100
10%
1594 ms
643 ms
1684 ms
1043 ms
1998 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 84% of them (42 requests) were addressed to the original Axure.org, 4% (2 requests) were made to Hm.baidu.com and 2% (1 request) were made to Webppd.com. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source C.cnzz.com.
Page size can be reduced by 143.5 kB (51%)
279.2 kB
135.7 kB
In fact, the total size of Axure.org main page is 279.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. 15% of websites need less resources to load. Images take 150.8 kB which makes up the majority of the site volume.
Potential reduce by 20.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 5.2 kB, which is 20% 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 20.3 kB or 80% of the original size.
Potential reduce by 56.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, Axure needs image optimization as it can save up to 56.2 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 63.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 63.1 kB or 65% of the original size.
Potential reduce by 3.9 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. Axure.org needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 73% of the original size.
Number of requests can be reduced by 9 (19%)
48
39
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Axure. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
axure.org
1594 ms
css.css
643 ms
jquery.min.js
1684 ms
hm.js
1043 ms
qq1.png
1998 ms
bg.gif
425 ms
webppd_axure.jpg
875 ms
u185_normal.jpg
1104 ms
arrow_down.gif
455 ms
u61_normal.gif
463 ms
u64_normal.gif
464 ms
u48_normal.gif
832 ms
u15_normal.gif
902 ms
u18_normal.gif
898 ms
axurepeixun.gif
915 ms
u147_normal.gif
1280 ms
chanpinguwen.gif
1308 ms
yuanxingsheji.gif
1310 ms
u153_normal.gif
1359 ms
mockplus.gif
1346 ms
vxplo.gif
1525 ms
mugeda.gif
1715 ms
u21_normal.gif
1749 ms
u90_normal.gif
1788 ms
yuejianyin.gif
1764 ms
u39_normal.gif
1778 ms
u12_normal.gif
1949 ms
u45_normal.gif
2151 ms
chinapm.gif
2170 ms
tucao.gif
2201 ms
u175_normal.gif
2223 ms
u135_normal.gif
2229 ms
pmjingying.gif
2427 ms
chuangye.gif
2582 ms
touziren.gif
2608 ms
u193_normal.gif
2621 ms
axure_org.png
3306 ms
baidu.html
2649 ms
u187_normal.gif
2889 ms
main_bg.gif
3000 ms
u209_normal.png
3026 ms
stat.php
2555 ms
u218_normal.png
2626 ms
axure8.png
3318 ms
hm.gif
478 ms
stat.htm
235 ms
core.php
3495 ms
baidubg.png
722 ms
9.gif
1798 ms
app.gif
882 ms
axure.org 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.
axure.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
axure.org 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 uses 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 Axure.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 Axure.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.
axure.org
Open Graph description is not detected on the main page of Axure. 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: