Tools & Wizards About Us
viewer.xbrl.us screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

viewer.xbrl.us

2016 US GAAP Financial Reporting Taxonomy - XBRL US

Page Load Speed

1.7 sec in total

First Response

17 ms

Resources Loaded

1.5 sec

Page Rendered

223 ms

viewer.xbrl.us screenshot

About Website

Click here to check amazing Viewer XBRL content for United States. Otherwise, check out these important facts you probably never knew about viewer.xbrl.us

The 2016 US GAAP Taxonomy was developed by the Financial Accounting Financial Board (FASB) and has been accepted and supported by the SEC. It can be downloaded…

Visit viewer.xbrl.us

Key Findings

We analyzed Viewer.xbrl.us page load time and found that the first response time was 17 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

viewer.xbrl.us performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value3,470 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.088

92/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

viewer.xbrl.us

17 ms

814 ms

font-awesome-4.1.min.css

65 ms

css

116 ms

css

143 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Viewer.xbrl.us, 48% (40 requests) were made to Xbrl.us and 27% (22 requests) were made to Cache.xbrl.us. The less responsive or slowest element that took the longest time to load (814 ms) relates to the external source Xbrl.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 456.0 kB (38%)

Content Size

1.2 MB

After Optimization

737.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Viewer.xbrl.us main page is 1.2 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. 70% of websites need less resources to load. Javascripts take 856.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 91.3 kB

  • Original 115.1 kB
  • After minification 111.5 kB
  • After compression 23.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 91.3 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 3.0 kB

  • Original 80.4 kB
  • After minification 77.4 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. Viewer XBRL images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 334.8 kB

  • Original 856.9 kB
  • After minification 856.9 kB
  • After compression 522.2 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 334.8 kB or 39% of the original size.

CSS Optimization

-19%

Potential reduce by 27.0 kB

  • Original 140.8 kB
  • After minification 126.8 kB
  • After compression 113.8 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. Viewer.xbrl.us needs all CSS files to be minified and compressed as it can save up to 27.0 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (84%)

Requests Now

77

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viewer XBRL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

viewer.xbrl.us

viewer.xbrl.us

17 ms

814 ms

font-awesome-4.1.min.css

font-awesome-4.1.min.css

65 ms

css

css

116 ms

css

css

143 ms

css

css

147 ms

css

css

151 ms

css

css

149 ms

training-template.css

training-template.css

109 ms

font-awesome-4.2.min.css

font-awesome-4.2.min.css

65 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

92 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

88 ms

bootstrap.min.js

bootstrap.min.js

108 ms

bootstrap.min.css

bootstrap.min.css

118 ms

list.min.js

list.min.js

123 ms

list.pagination.min.js

list.pagination.min.js

126 ms

font-awesome.min.css

font-awesome.min.css

113 ms

style.min.css

style.min.css

129 ms

blocks.style.build.css

blocks.style.build.css

90 ms

style.min.css

style.min.css

128 ms

style.min.css

style.min.css

127 ms

style.min.css

style.min.css

130 ms

style.min.css

style.min.css

134 ms

style.min.css

style.min.css

132 ms

style.min.css

style.min.css

134 ms

bbpress.min.css

bbpress.min.css

87 ms

styles.css

styles.css

87 ms

style.front.css

style.front.css

87 ms

woocommerce-layout.css

woocommerce-layout.css

88 ms

woocommerce.css

woocommerce.css

102 ms

badgeos-single.min.css

badgeos-single.min.css

103 ms

h5p.css

h5p.css

104 ms

visitor.css

visitor.css

132 ms

upw-theme-standard.min.css

upw-theme-standard.min.css

103 ms

jquery.fancybox.css

jquery.fancybox.css

92 ms

front.css

front.css

104 ms

jquery.min.js

jquery.min.js

109 ms

jquery-migrate.min.js

jquery-migrate.min.js

109 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

109 ms

js.cookie.min.js

js.cookie.min.js

110 ms

woocommerce.min.js

woocommerce.min.js

110 ms

js

js

244 ms

front.min.js

front.min.js

117 ms

style.css

style.css

132 ms

in.js

in.js

104 ms

bubble.js

bubble.js

243 ms

wc-blocks.css

wc-blocks.css

116 ms

badgeos-front.min.css

badgeos-front.min.css

116 ms

api-ajax.js

api-ajax.js

110 ms

index.js

index.js

115 ms

index.js

index.js

110 ms

sourcebuster.min.js

sourcebuster.min.js

120 ms

order-attribution.min.js

order-attribution.min.js

118 ms

api-ajax.js

api-ajax.js

126 ms

jquery.fancybox.js

jquery.fancybox.js

125 ms

jquery.mousewheel.js

jquery.mousewheel.js

111 ms

api.js

api.js

121 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

111 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

113 ms

wp-polyfill.min.js

wp-polyfill.min.js

118 ms

index.js

index.js

117 ms

style-xus.css

style-xus.css

44 ms

logoHeader-US.png

logoHeader-US.png

123 ms

blocks.style.build.css

blocks.style.build.css

33 ms

bar.png

bar.png

47 ms

iconSearch.png

iconSearch.png

36 ms

logoFooter.png

logoFooter.png

38 ms

facebook.png

facebook.png

46 ms

twitter.png

twitter.png

36 ms

linkedin.png

linkedin.png

37 ms

rss.png

rss.png

46 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

26 ms

font

font

46 ms

font

font

39 ms

widgets.js

widgets.js

126 ms

recaptcha__en.js

recaptcha__en.js

64 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

61 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

28 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

37 ms

sdk.js

sdk.js

60 ms

bubble.css

bubble.css

103 ms

sdk.js

sdk.js

60 ms

count.json

count.json

67 ms

Accessibility Review

viewer.xbrl.us accessibility score

87

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

viewer.xbrl.us best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

viewer.xbrl.us SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Viewer.xbrl.us can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Viewer.xbrl.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.

Social Sharing Optimization

viewer.xbrl.us

Open Graph data is detected on the main page of Viewer XBRL. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: