Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

iwuf.org

主页 - IWUF

Page Load Speed

8.6 sec in total

First Response

668 ms

Resources Loaded

7.5 sec

Page Rendered

425 ms

iwuf.org screenshot

About Website

Click here to check amazing IWUF content for Russia. Otherwise, check out these important facts you probably never knew about iwuf.org

International Wushu Federation

Visit iwuf.org

Key Findings

We analyzed Iwuf.org page load time and found that the first response time was 668 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

iwuf.org performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value33.7 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.422

23/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

iwuf.org

668 ms

base.css

529 ms

common.css

529 ms

index.css

531 ms

senro.css

532 ms

Our browser made a total of 170 requests to load all elements on the main page. We found that 94% of them (160 requests) were addressed to the original Iwuf.org, 4% (6 requests) were made to Static.woniu.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.8 sec) relates to the external source Gg.woniu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (7%)

Content Size

18.6 MB

After Optimization

17.3 MB

In fact, the total size of Iwuf.org main page is 18.6 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 17.8 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 96.8 kB

  • Original 106.2 kB
  • After minification 74.2 kB
  • After compression 9.4 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 32.0 kB, which is 30% 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 96.8 kB or 91% of the original size.

Image Optimization

-4%

Potential reduce by 687.9 kB

  • Original 17.8 MB
  • After minification 17.1 MB

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. IWUF images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 480.0 kB

  • Original 633.6 kB
  • After minification 481.8 kB
  • After compression 153.6 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 480.0 kB or 76% of the original size.

CSS Optimization

-81%

Potential reduce by 23.9 kB

  • Original 29.4 kB
  • After minification 19.3 kB
  • After compression 5.5 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. Iwuf.org needs all CSS files to be minified and compressed as it can save up to 23.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (8%)

Requests Now

169

After Optimization

156

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

Accessibility Review

iwuf.org accessibility score

77

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 input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

High

Some elements have a [tabindex] value greater than 0

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>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

iwuf.org 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

iwuf.org SEO score

84

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Iwuf.org 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 Iwuf.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.

Social Sharing Optimization

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