Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

june29.jp

#june29jp

Page Load Speed

12.3 sec in total

First Response

1.5 sec

Resources Loaded

8.4 sec

Page Rendered

2.4 sec

june29.jp screenshot

About Website

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

june29's official website

Visit june29.jp

Key Findings

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

Performance Metrics

june29.jp performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value4,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

june29.jp

1506 ms

base.css

336 ms

HatenaStar.js

935 ms

widgets.js

84 ms

bookmark_button.js

508 ms

Our browser made a total of 242 requests to load all elements on the main page. We found that 3% of them (8 requests) were addressed to the original June29.jp, 52% (125 requests) were made to Speakerd.s3.amazonaws.com and 5% (11 requests) were made to Public.slidesharecdn.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source S.hatena.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (14%)

Content Size

7.3 MB

After Optimization

6.3 MB

In fact, the total size of June29.jp main page is 7.3 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. 80% 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 6.1 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 50.9 kB

  • Original 70.3 kB
  • After minification 68.8 kB
  • After compression 19.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. 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 50.9 kB or 72% of the original size.

Image Optimization

-4%

Potential reduce by 231.3 kB

  • Original 6.1 MB
  • After minification 5.9 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. June 29 images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 680.1 kB

  • Original 993.4 kB
  • After minification 922.2 kB
  • After compression 313.3 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 680.1 kB or 68% of the original size.

CSS Optimization

-74%

Potential reduce by 102.2 kB

  • Original 137.5 kB
  • After minification 133.5 kB
  • After compression 35.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. June29.jp needs all CSS files to be minified and compressed as it can save up to 102.2 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (25%)

Requests Now

239

After Optimization

180

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

Accessibility Review

june29.jp accessibility score

77

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

Image elements do not have [alt] attributes

Best Practices

june29.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

june29.jp SEO score

90

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise June29.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 June29.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 June 29. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: