Tools & Wizards About Us
studiozoo.jp screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

studiozoo.jp

スタジオ ZOO 【名古屋　ダンススタジオ】

Page Load Speed

5.6 sec in total

First Response

595 ms

Resources Loaded

4.7 sec

Page Rendered

354 ms

studiozoo.jp screenshot

About Website

Click here to check amazing Studio ZOO content. Otherwise, check out these important facts you probably never knew about studiozoo.jp

ダンススクール/名古屋市中区栄 ダンススタジオ「ZOO」

Visit studiozoo.jp

Key Findings

We analyzed Studiozoo.jp page load time and found that the first response time was 595 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

studiozoo.jp performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

studiozoo.jp

595 ms

www.studiozoo.jp

1162 ms

style.css

355 ms

luminous-basic.min.css

27 ms

style.min.css

541 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 73% of them (45 requests) were addressed to the original Studiozoo.jp, 11% (7 requests) were made to Cdn.jsdelivr.net and 6% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Studiozoo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 103.6 kB (12%)

Content Size

896.0 kB

After Optimization

792.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Studiozoo.jp main page is 896.0 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. 30% of websites need less resources to load. Images take 493.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 45.0 kB

  • Original 55.4 kB
  • After minification 45.4 kB
  • After compression 10.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 10.0 kB, which is 18% 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 45.0 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 24.1 kB

  • Original 493.3 kB
  • After minification 469.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. Studio ZOO images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 33.7 kB

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

CSS Optimization

-3%

Potential reduce by 755 B

  • Original 23.0 kB
  • After minification 23.0 kB
  • After compression 22.2 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. Studiozoo.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (47%)

Requests Now

59

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

studiozoo.jp

studiozoo.jp

595 ms

www.studiozoo.jp

www.studiozoo.jp

1162 ms

style.css

style.css

355 ms

luminous-basic.min.css

luminous-basic.min.css

27 ms

style.min.css

style.min.css

541 ms

styles.css

styles.css

687 ms

slick.css

slick.css

21 ms

slick-theme.css

slick-theme.css

23 ms

jquery.min.js

jquery.min.js

17 ms

slick.min.js

slick.min.js

11 ms

gsap.min.js

gsap.min.js

763 ms

plugin.js

plugin.js

1301 ms

common.js

common.js

610 ms

luminous.min.js

luminous.min.js

11 ms

index.js

index.js

704 ms

hooks.min.js

hooks.min.js

788 ms

i18n.min.js

i18n.min.js

794 ms

index.js

index.js

792 ms

index.js

index.js

882 ms

css2

css2

34 ms

embed

embed

216 ms

logo.jpg

logo.jpg

721 ms

header_tel.png

header_tel.png

750 ms

fv_txt03.png

fv_txt03.png

929 ms

slide_bnr_01.jpg

slide_bnr_01.jpg

928 ms

slide_bnr_03.jpg

slide_bnr_03.jpg

1011 ms

slide_bnr_02-1.jpg

slide_bnr_02-1.jpg

1077 ms

slide_bnr_04_2.jpg

slide_bnr_04_2.jpg

1278 ms

slide_bnr_05.jpg

slide_bnr_05.jpg

1145 ms

phonto-10-e1710248874453.jpeg

phonto-10-e1710248874453.jpeg

1146 ms

phonto-17-e1710931291363.jpeg

phonto-17-e1710931291363.jpeg

1192 ms

phonto-e1719933741669.jpeg

phonto-e1719933741669.jpeg

1259 ms

IMG_4772-e1719933077996.jpeg

IMG_4772-e1719933077996.jpeg

1260 ms

IMG_6321-e1721994364325.jpeg

IMG_6321-e1721994364325.jpeg

1289 ms

IMG_0689-1-e1722058211432.jpeg

IMG_0689-1-e1722058211432.jpeg

1294 ms

section02_slide01.webp

section02_slide01.webp

1371 ms

section02_slide03.webp

section02_slide03.webp

1441 ms

section02_slide05.webp

section02_slide05.webp

1439 ms

section02_slide08.webp

section02_slide08.webp

1456 ms

section02_slide10.webp

section02_slide10.webp

1472 ms

section03_image01.webp

section03_image01.webp

1474 ms

ico_tw.png

ico_tw.png

1547 ms

ico_fb.png

ico_fb.png

1620 ms

ico_ig.png

ico_ig.png

1620 ms

footer_logo.jpg

footer_logo.jpg

1635 ms

ico_btn_line.png

ico_btn_line.png

1653 ms

js

js

35 ms

geometry.js

geometry.js

4 ms

search.js

search.js

7 ms

main.js

main.js

13 ms

section02_bg.jpg

section02_bg.jpg

1522 ms

dot.png

dot.png

1420 ms

ico_btn_tel.png

ico_btn_tel.png

1423 ms

font

font

43 ms

font

font

73 ms

font

font

74 ms

ico_btn_ig.png

ico_btn_ig.png

1420 ms

ico_btn_mail.png

ico_btn_mail.png

1339 ms

ajax-loader.gif

ajax-loader.gif

23 ms

slide_prev.png

slide_prev.png

697 ms

slide_next.png

slide_next.png

769 ms

slick.woff

slick.woff

27 ms

Accessibility Review

studiozoo.jp accessibility score

68

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

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

studiozoo.jp 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

High

Missing source maps for large first-party JavaScript

SEO Factors

studiozoo.jp SEO score

83

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

studiozoo.jp

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