Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

happines.blue

共働き主婦の時短の暮らし | ワーキングマザー。時短の家事と料理の(作り置き)ミニマリストへの道(断捨離)シンプルライフ。家計のこと

Page Load Speed

8.8 sec in total

First Response

1.5 sec

Resources Loaded

6.6 sec

Page Rendered

826 ms

happines.blue screenshot

About Website

Welcome to happines.blue homepage info - get ready to check Happines best content for Japan right away, or after learning these important things about happines.blue

ご無沙汰のブログになってしまいました。 私事ですが、長男の中学受験が終わりました。 長いようで短い、短いようで長い受験生活が 1月中旬をもちまして4年間という 塾生活から解放されました。 長男は小学2年(8歳)から一人で電車に乗り 30分かけて塾へ通っていました。 私は最寄りの駅までのお迎えや、 塾のお弁当も作り、

Visit happines.blue

Key Findings

We analyzed Happines.blue page load time and found that the first response time was 1.5 sec and then it took 7.4 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

happines.blue performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value22.6 s

0/100

10%

TBT (Total Blocking Time)

Value47,940 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value63.3 s

0/100

10%

Network Requests Diagram

happines.blue

1455 ms

style.css

352 ms

responsive-pc.css

350 ms

font-awesome.min.css

346 ms

style.css

371 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 35% of them (30 requests) were addressed to the original Happines.blue, 9% (8 requests) were made to Googleads.g.doubleclick.net and 9% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source S.eximg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 140.1 kB (22%)

Content Size

635.9 kB

After Optimization

495.8 kB

In fact, the total size of Happines.blue main page is 635.9 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. 75% 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 311.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 98.2 kB

  • Original 121.1 kB
  • After minification 117.0 kB
  • After compression 22.9 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 98.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 325 B

  • Original 311.4 kB
  • After minification 311.1 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. Happines images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 35.6 kB

  • Original 168.1 kB
  • After minification 168.1 kB
  • After compression 132.5 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 35.6 kB or 21% of the original size.

CSS Optimization

-17%

Potential reduce by 5.9 kB

  • Original 35.3 kB
  • After minification 35.0 kB
  • After compression 29.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. Happines.blue needs all CSS files to be minified and compressed as it can save up to 5.9 kB or 17% of the original size.

Requests Breakdown

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

Requests Now

76

After Optimization

28

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

Accessibility Review

happines.blue accessibility score

72

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

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

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

<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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

happines.blue best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

happines.blue SEO score

86

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Happines.blue 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 Happines.blue 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 Happines. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: