Tools & Wizards About Us
push7.jp screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

push7.jp

Webプッシュ通知を5分で導入 - 効果を求めるならPush7‎

Page Load Speed

5.6 sec in total

First Response

665 ms

Resources Loaded

3.2 sec

Page Rendered

1.7 sec

push7.jp screenshot

About Website

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

Push7は国内10,000サイトへ導入されたWebプッシュ通知サービスです。5分で導入ができ、データベースと連動したセグメント配信も可能です。大規模な会員制サイトからウェブマガジンまで幅広いユースケースでエンゲージメントを高めるご支援をいたします。

Visit push7.jp

Key Findings

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

Performance Metrics

push7.jp performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

81/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

push7.jp

665 ms

push7.jp

921 ms

gtm.js

84 ms

c96bdc71e2e206563ac8.js

191 ms

ca3607c7afd7c284e1ad.js

369 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 97% of them (35 requests) were addressed to the original Push7.jp, 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Push7.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 78.2 kB (52%)

Content Size

151.4 kB

After Optimization

73.3 kB

  • HTML
  • Images

In fact, the total size of Push7.jp main page is 151.4 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. 25% of websites need less resources to load. HTML takes 100.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 78.2 kB

  • Original 100.7 kB
  • After minification 100.5 kB
  • After compression 22.5 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 78.2 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 50.8 kB
  • After minification 50.8 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. Push 7 images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 5 (15%)

Requests Now

34

After Optimization

29

  • Images
  • JavaScript

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

Network Requests Diagram

push7.jp

push7.jp

665 ms

push7.jp

push7.jp

921 ms

gtm.js

gtm.js

84 ms

c96bdc71e2e206563ac8.js

c96bdc71e2e206563ac8.js

191 ms

ca3607c7afd7c284e1ad.js

ca3607c7afd7c284e1ad.js

369 ms

e303450317dc09376bd4.js

e303450317dc09376bd4.js

721 ms

3f983af48914bf34c167.js

3f983af48914bf34c167.js

799 ms

138ca7029a1a404b48b0.js

138ca7029a1a404b48b0.js

802 ms

ef960d1.svg

ef960d1.svg

637 ms

a698887.svg

a698887.svg

667 ms

26e959b.png

26e959b.png

884 ms

c129209.svg

c129209.svg

840 ms

1a43e63.svg

1a43e63.svg

885 ms

1aee03b.svg

1aee03b.svg

894 ms

4539631.svg

4539631.svg

992 ms

4ba7e79.svg

4ba7e79.svg

993 ms

bed8cc9.svg

bed8cc9.svg

1040 ms

174cb6b.svg

174cb6b.svg

1101 ms

f79e751.svg

f79e751.svg

1103 ms

1913b66.svg

1913b66.svg

1068 ms

5299bf2.svg

5299bf2.svg

1185 ms

478f853.svg

478f853.svg

1183 ms

93a7b42.svg

93a7b42.svg

1241 ms

d47a5a6.svg

d47a5a6.svg

1243 ms

1a87aa9.svg

1a87aa9.svg

1319 ms

e8a664b.svg

e8a664b.svg

1322 ms

6e0246d.svg

6e0246d.svg

1377 ms

5ee7f14.svg

5ee7f14.svg

1375 ms

25937d1.svg

25937d1.svg

1444 ms

0e575a4.svg

0e575a4.svg

1416 ms

0ff2414.svg

0ff2414.svg

1539 ms

eff591e.svg

eff591e.svg

1541 ms

f75f1ce.svg

f75f1ce.svg

1567 ms

22e66a2.png

22e66a2.png

1566 ms

9f2644d.svg

9f2644d.svg

1590 ms

7379d7c.svg

7379d7c.svg

1647 ms

Accessibility Review

push7.jp accessibility score

59

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

Form elements do not have associated labels

Best Practices

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

SEO Factors

push7.jp SEO score

82

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

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

push7.jp

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