Tools & Wizards About Us
share.axure.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

share.axure.com

Farewell, Axure Share - Axure

Page Load Speed

746 ms in total

First Response

29 ms

Resources Loaded

609 ms

Page Rendered

108 ms

share.axure.com screenshot

About Website

Welcome to share.axure.com homepage info - get ready to check Share Axure best content for China right away, or after learning these important things about share.axure.com

Axure Share is now Axure Cloud. All of your projects that were in Axure Share are now hosted in Axure Cloud and can be accessed there.

Visit share.axure.com

Key Findings

We analyzed Share.axure.com page load time and found that the first response time was 29 ms and then it took 717 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

share.axure.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value3,800 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.062

97/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

share.axure.com

29 ms

share.axure.com

84 ms

jquery-ui-themes.css

28 ms

axure_rp_page.css

31 ms

styles.css

55 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 68% of them (43 requests) were addressed to the original Share.axure.com, 8% (5 requests) were made to D26uhratvi024l.cloudfront.net and 6% (4 requests) were made to Accounts.axure.com. The less responsive or slowest element that took the longest time to load (219 ms) belongs to the original domain Share.axure.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 74.0 kB (62%)

Content Size

118.5 kB

After Optimization

44.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Share.axure.com main page is 118.5 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. 35% of websites need less resources to load. Javascripts take 66.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 24.9 kB

  • Original 29.0 kB
  • After minification 23.1 kB
  • After compression 4.1 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.9 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 24.9 kB or 86% of the original size.

Image Optimization

-73%

Potential reduce by 15.5 kB

  • Original 21.4 kB
  • After minification 5.9 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, Share Axure needs image optimization as it can save up to 15.5 kB or 73% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-49%

Potential reduce by 32.6 kB

  • Original 66.7 kB
  • After minification 60.9 kB
  • After compression 34.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 32.6 kB or 49% of the original size.

CSS Optimization

-70%

Potential reduce by 1.0 kB

  • Original 1.4 kB
  • After minification 658 B
  • After compression 422 B

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. Share.axure.com needs all CSS files to be minified and compressed as it can save up to 1.0 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (80%)

Requests Now

60

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Share 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 39 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

share.axure.com

share.axure.com

29 ms

share.axure.com

share.axure.com

84 ms

jquery-ui-themes.css

jquery-ui-themes.css

28 ms

axure_rp_page.css

axure_rp_page.css

31 ms

styles.css

styles.css

55 ms

styles.css

styles.css

141 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

36 ms

jquery-ui-1.8.10.custom.min.js

jquery-ui-1.8.10.custom.min.js

36 ms

axQuery.js

axQuery.js

44 ms

globals.js

globals.js

36 ms

axutils.js

axutils.js

46 ms

annotation.js

annotation.js

59 ms

axQuery.std.js

axQuery.std.js

56 ms

doc.js

doc.js

57 ms

document.js

document.js

115 ms

messagecenter.js

messagecenter.js

72 ms

events.js

events.js

79 ms

action.js

action.js

70 ms

expr.js

expr.js

89 ms

geometry.js

geometry.js

81 ms

flyout.js

flyout.js

91 ms

ie.js

ie.js

98 ms

model.js

model.js

93 ms

repeater.js

repeater.js

125 ms

sto.js

sto.js

110 ms

utils.temp.js

utils.temp.js

103 ms

variables.js

variables.js

116 ms

drag.js

drag.js

114 ms

move.js

move.js

127 ms

visibility.js

visibility.js

124 ms

style.js

style.js

134 ms

adaptive.js

adaptive.js

172 ms

tree.js

tree.js

135 ms

init.temp.js

init.temp.js

172 ms

data.js

data.js

190 ms

legacy.js

legacy.js

175 ms

viewer.js

viewer.js

175 ms

axAccount.js

axAccount.js

38 ms

nexa_lightregular.css

nexa_lightregular.css

219 ms

axshareUtils.js

axshareUtils.js

149 ms

jquery.axDialog.js

jquery.axDialog.js

148 ms

sha512-min.js

sha512-min.js

144 ms

custom_AxshareLogin7_a.js

custom_AxshareLogin7_a.js

143 ms

ga.js

ga.js

73 ms

i.js

i.js

31 ms

88bd6c50e3bda46208a859890bb09fe00c23c34a.1.js

88bd6c50e3bda46208a859890bb09fe00c23c34a.1.js

176 ms

u1.gif

u1.gif

125 ms

transparent.gif

transparent.gif

123 ms

u23_line.png

u23_line.png

128 ms

u24.png

u24.png

157 ms

style.css

style.css

29 ms

Dialogs.html

Dialogs.html

42 ms

auth

auth

46 ms

u28.png

u28.png

58 ms

u30.png

u30.png

66 ms

u52.gif

u52.gif

73 ms

createaccount_u78.png

createaccount_u78.png

77 ms

__utm.gif

__utm.gif

33 ms

u26.png

u26.png

72 ms

u74.png

u74.png

84 ms

login_u76.png

login_u76.png

51 ms

prototypego_u80.png

prototypego_u80.png

67 ms

Nexa_Light-webfont.woff

Nexa_Light-webfont.woff

46 ms

Accessibility Review

share.axure.com accessibility score

94

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-hidden="true"] elements contain focusable descendents

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.

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

Links do not have a discernible name

Best Practices

share.axure.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

share.axure.com SEO score

86

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

Social Sharing Optimization

share.axure.com

Open Graph description is not detected on the main page of Share 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: