Tools & Wizards About Us

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

hamazoo.net

浜松市動物園情報サイト／わくわく！はまＺＯＯ／NPO法人浜松市動物園協会

Page Load Speed

4.7 sec in total

First Response

1.1 sec

Resources Loaded

3.2 sec

Page Rendered

314 ms

About Website

Welcome to hamazoo.net homepage info - get ready to check Hamazoo best content for Japan right away, or after learning these important things about hamazoo.net

浜松市動物園公式情報ページです。ニュース/イベントカレンダー/飼育員ブログ/動物たちの映像コンテンツ　など

Visit hamazoo.net

Key Findings

We analyzed Hamazoo.net page load time and found that the first response time was 1.1 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

hamazoo.net performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.648

9/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

hamazoo.net

1118 ms

standard.css

479 ms

top.css

335 ms

alphafilter.js

339 ms

jquery.min.js

7 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 78% of them (52 requests) were addressed to the original Hamazoo.net, 13% (9 requests) were made to Google.com and 4% (3 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Hamazoo.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.9 kB (21%)

Content Size

693.1 kB

After Optimization

544.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hamazoo.net main page is 693.1 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. Images take 476.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 42.2 kB

  • Original 51.2 kB
  • After minification 49.4 kB
  • After compression 9.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 42.2 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 25.8 kB

  • Original 476.8 kB
  • After minification 451.0 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. Hamazoo images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 48.7 kB

  • Original 125.7 kB
  • After minification 120.4 kB
  • After compression 77.0 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 48.7 kB or 39% of the original size.

CSS Optimization

-82%

Potential reduce by 32.2 kB

  • Original 39.5 kB
  • After minification 31.2 kB
  • After compression 7.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. Hamazoo.net needs all CSS files to be minified and compressed as it can save up to 32.2 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

64

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

hamazoo.net accessibility score

80

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

hamazoo.net 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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hamazoo.net SEO score

77

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hamazoo.net 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 Hamazoo.net main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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