Tools & Wizards About Us
uzume.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

uzume.com

Uzume Taiko | Uzume Taiko

Page Load Speed

3.2 sec in total

First Response

181 ms

Resources Loaded

2.6 sec

Page Rendered

372 ms

uzume.com screenshot

About Website

Visit uzume.com now to see the best up-to-date Uzume content and also check out these interesting facts you probably never knew about uzume.com

Visit uzume.com

Key Findings

We analyzed Uzume.com page load time and found that the first response time was 181 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

uzume.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.448

20/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

uzume.com

181 ms

uzume.com

305 ms

www.uzume.com

324 ms

js

94 ms

font.css

92 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 96% of them (106 requests) were addressed to the original Uzume.com, 2% (2 requests) were made to Stackpath.bootstrapcdn.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (944 ms) belongs to the original domain Uzume.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.0 kB (5%)

Content Size

2.5 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Uzume.com main page is 2.5 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. 45% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 26.8 kB

  • Original 34.8 kB
  • After minification 32.9 kB
  • After compression 8.0 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 26.8 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 91.4 kB

  • Original 2.4 MB
  • After minification 2.3 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. Uzume images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 5.7 kB

  • Original 54.8 kB
  • After minification 54.8 kB
  • After compression 49.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. This website has mostly compressed JavaScripts.

CSS Optimization

-30%

Potential reduce by 7.1 kB

  • Original 23.4 kB
  • After minification 21.2 kB
  • After compression 16.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. Uzume.com needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 89 (86%)

Requests Now

104

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

uzume.com

uzume.com

181 ms

uzume.com

uzume.com

305 ms

www.uzume.com

www.uzume.com

324 ms

js

js

94 ms

font.css

font.css

92 ms

font.css

font.css

166 ms

font.css

font.css

231 ms

paragraphs_and_lists.css

paragraphs_and_lists.css

227 ms

titles.css

titles.css

229 ms

superfish.css

superfish.css

233 ms

ajax-progress.module.css

ajax-progress.module.css

240 ms

align.module.css

align.module.css

243 ms

autocomplete-loading.module.css

autocomplete-loading.module.css

298 ms

fieldgroup.module.css

fieldgroup.module.css

297 ms

container-inline.module.css

container-inline.module.css

300 ms

clearfix.module.css

clearfix.module.css

302 ms

details.module.css

details.module.css

312 ms

hidden.module.css

hidden.module.css

316 ms

item-list.module.css

item-list.module.css

373 ms

js.module.css

js.module.css

369 ms

nowrap.module.css

nowrap.module.css

374 ms

position-container.module.css

position-container.module.css

373 ms

progress.module.css

progress.module.css

386 ms

reset-appearance.module.css

reset-appearance.module.css

389 ms

resize.module.css

resize.module.css

442 ms

sticky-header.module.css

sticky-header.module.css

441 ms

system-status-counter.css

system-status-counter.css

444 ms

system-status-report-counters.css

system-status-report-counters.css

445 ms

system-status-report-general-info.css

system-status-report-general-info.css

461 ms

tabledrag.module.css

tabledrag.module.css

468 ms

tablesort.module.css

tablesort.module.css

514 ms

tree-child.module.css

tree-child.module.css

514 ms

views.module.css

views.module.css

515 ms

filter.caption.css

filter.caption.css

518 ms

filter.caption.css

filter.caption.css

533 ms

back_to_top.css

back_to_top.css

541 ms

white.css

white.css

584 ms

variables.css

variables.css

583 ms

user.css

user.css

587 ms

bootstrap.min.css

bootstrap.min.css

94 ms

popper.min.js

popper.min.js

102 ms

bootstrap.min.js

bootstrap.min.js

105 ms

progress.css

progress.css

575 ms

affix.css

affix.css

524 ms

book.css

book.css

459 ms

contextual.css

contextual.css

433 ms

feed-icon.css

feed-icon.css

434 ms

field.css

field.css

435 ms

header.css

header.css

433 ms

help.css

help.css

447 ms

icons.css

icons.css

454 ms

image-button.css

image-button.css

432 ms

item-list.css

item-list.css

435 ms

list-group.css

list-group.css

433 ms

media.css

media.css

435 ms

page.css

page.css

448 ms

search-form.css

search-form.css

454 ms

shortcut.css

shortcut.css

431 ms

sidebar.css

sidebar.css

431 ms

site-footer.css

site-footer.css

430 ms

skip-link.css

skip-link.css

432 ms

table.css

table.css

449 ms

tabledrag.css

tabledrag.css

457 ms

tableselect.css

tableselect.css

429 ms

tablesort-indicator.css

tablesort-indicator.css

434 ms

ui.widget.css

ui.widget.css

428 ms

tabs.css

tabs.css

432 ms

toolbar.css

toolbar.css

451 ms

vertical-tabs.css

vertical-tabs.css

451 ms

views.css

views.css

430 ms

webform.css

webform.css

438 ms

ui-dialog.css

ui-dialog.css

437 ms

style.css

style.css

434 ms

colors.css

colors.css

454 ms

white.css

white.css

454 ms

messages-white.css

messages-white.css

432 ms

styles-12821ffddf69c43c59f70bfb77426b93.css

styles-12821ffddf69c43c59f70bfb77426b93.css

439 ms

jquery.min.js

jquery.min.js

516 ms

once.min.js

once.min.js

480 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

463 ms

drupal.js

drupal.js

457 ms

drupal.init.js

drupal.init.js

435 ms

back_to_top.js

back_to_top.js

448 ms

google_analytics.js

google_analytics.js

462 ms

barrio.js

barrio.js

476 ms

global.js

global.js

467 ms

superfish.js

superfish.js

466 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

444 ms

sftouchscreen.js

sftouchscreen.js

452 ms

sfsmallscreen.js

sfsmallscreen.js

461 ms

supposition.js

supposition.js

479 ms

supersubs.js

supersubs.js

468 ms

superfish.js

superfish.js

464 ms

uzume-taiko-logo-400.png

uzume-taiko-logo-400.png

509 ms

170317%20Uzume%20Taiko%20-%20%28A%29Live%20in%20Concert%2020-20-04%20-%20Photo%20by%20Adam%20PW%20Smith.jpg

170317%20Uzume%20Taiko%20-%20%28A%29Live%20in%20Concert%2020-20-04%20-%20Photo%20by%20Adam%20PW%20Smith.jpg

657 ms

IN-PERSON%20STUDIO%20CLASSES%20hero%20shot.jpg

IN-PERSON%20STUDIO%20CLASSES%20hero%20shot.jpg

944 ms

Jumping%20Quartet.jpg

Jumping%20Quartet.jpg

870 ms

Distance%20Learning%20Workshops_0.gif

Distance%20Learning%20Workshops_0.gif

831 ms

Slide%20Uzume%20Workshops.jpg

Slide%20Uzume%20Workshops.jpg

598 ms

BC%20logo.png

BC%20logo.png

507 ms

CCA_RGB_colour_e.jpg

CCA_RGB_colour_e.jpg

577 ms

City%20of%20Van%20logo.png

City%20of%20Van%20logo.png

639 ms

BOOK%20A%20PERFORMANCE%20%281%29.jpg

BOOK%20A%20PERFORMANCE%20%281%29.jpg

712 ms

BOOK%20A%20WORKSHOP.jpg

BOOK%20A%20WORKSHOP.jpg

632 ms

donate-now.png

donate-now.png

665 ms

background-uzume-taiko-stage-group.jpg

background-uzume-taiko-stage-group.jpg

586 ms

font.woff

font.woff

653 ms

font.woff

font.woff

662 ms

font.woff

font.woff

622 ms

print.css

print.css

78 ms

Accessibility Review

uzume.com accessibility score

93

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.

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

uzume.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

uzume.com SEO score

86

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

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 Uzume.com 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 Uzume.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

uzume.com

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