Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

3004.jp

Yamada3004 BLOG - 東京 墨田区 下町 フリーランスのWeb屋 やまだみちよのブログ

Page Load Speed

12.3 sec in total

First Response

4 sec

Resources Loaded

7.5 sec

Page Rendered

736 ms

3004.jp screenshot

About Website

Click here to check amazing 3004 content for Japan. Otherwise, check out these important facts you probably never knew about 3004.jp

東京都墨田区 フリーランスのWebクリエイタ―やまだみちよのブログ。Web制作や音楽、映画のことなど気ままに更新中。

Visit 3004.jp

Key Findings

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

Performance Metrics

3004.jp performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.0 s

77/100

10%

Network Requests Diagram

3004.jp

4015 ms

style.css

186 ms

font.css

316 ms

font-awesome.min.css

16 ms

styles.css

317 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 36% of them (25 requests) were addressed to the original 3004.jp, 29% (20 requests) were made to Scontent.cdninstagram.com and 14% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain 3004.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 346.7 kB (6%)

Content Size

5.8 MB

After Optimization

5.4 MB

In fact, the total size of 3004.jp main page is 5.8 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 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 20.4 kB

  • Original 28.2 kB
  • After minification 27.6 kB
  • After compression 7.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. 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 20.4 kB or 72% of the original size.

Image Optimization

-2%

Potential reduce by 106.6 kB

  • Original 5.4 MB
  • After minification 5.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. 3004 images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 120.3 kB

  • Original 235.1 kB
  • After minification 232.0 kB
  • After compression 114.9 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 120.3 kB or 51% of the original size.

CSS Optimization

-81%

Potential reduce by 99.4 kB

  • Original 122.8 kB
  • After minification 111.7 kB
  • After compression 23.4 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. 3004.jp needs all CSS files to be minified and compressed as it can save up to 99.4 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

58

After Optimization

30

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 3004. 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 11 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

3004.jp accessibility score

88

Accessibility Issues

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

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

SEO Factors

3004.jp SEO score

86

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

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 3004.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 3004.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 3004. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: