Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

hama2.jp

浜松つーしん - 浜松のいろんな話題が集まるメディア

Page Load Speed

7.1 sec in total

First Response

955 ms

Resources Loaded

4.7 sec

Page Rendered

1.4 sec

hama2.jp screenshot

About Website

Visit hama2.jp now to see the best up-to-date Hama 2 content for Japan and also check out these interesting facts you probably never knew about hama2.jp

浜松つーしん(はまつー)は、浜松市に特化したニュース、グルメ、イベント、お店の開店閉店情報、浜松市民しかわからない地元ネタ、話題、雑談ネタなどを幅広く紹介する地域情報サイトです。情報提供も大歓迎です。

Visit hama2.jp

Key Findings

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

Performance Metrics

hama2.jp performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value2,140 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

hama2.jp

955 ms

template.css

343 ms

site.css

333 ms

import.js

346 ms

c2.js

357 ms

Our browser made a total of 144 requests to load all elements on the main page. We found that 6% of them (8 requests) were addressed to the original Hama2.jp, 42% (61 requests) were made to Resize.blogsys.jp and 12% (17 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Encrypted-tbn0.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 322.1 kB (15%)

Content Size

2.1 MB

After Optimization

1.8 MB

In fact, the total size of Hama2.jp main page is 2.1 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 141.5 kB

  • Original 169.3 kB
  • After minification 133.5 kB
  • After compression 27.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. This page needs HTML code to be minified as it can gain 35.8 kB, which is 21% 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 141.5 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 44.0 kB

  • Original 1.7 MB
  • After minification 1.7 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. Hama 2 images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 91.2 kB

  • Original 216.4 kB
  • After minification 205.1 kB
  • After compression 125.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 91.2 kB or 42% of the original size.

CSS Optimization

-83%

Potential reduce by 45.4 kB

  • Original 54.5 kB
  • After minification 41.0 kB
  • After compression 9.1 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. Hama2.jp needs all CSS files to be minified and compressed as it can save up to 45.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (27%)

Requests Now

138

After Optimization

101

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

Accessibility Review

hama2.jp accessibility score

90

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

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.

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

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

hama2.jp SEO score

99

Search Engine Optimization Advices

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

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