Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

smamori.jp

子供スマホ使用管理アプリ「スマモリ」

Page Load Speed

7.6 sec in total

First Response

1.1 sec

Resources Loaded

5.6 sec

Page Rendered

881 ms

smamori.jp screenshot

About Website

Welcome to smamori.jp homepage info - get ready to check Smamori best content for Japan right away, or after learning these important things about smamori.jp

お子様のスマホが心配ですか?スマモリならスマホをモニタリングし、使用時間の制限や有害サイトのフィルタリングをすることで使いすぎを防げます。まずは無料お試しから

Visit smamori.jp

Key Findings

We analyzed Smamori.jp page load time and found that the first response time was 1.1 sec and then it took 6.5 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

smamori.jp performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value25.0 s

0/100

25%

SI (Speed Index)

Value17.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.8 s

1/100

10%

Network Requests Diagram

smamori.jp

1070 ms

vendor_blue_10.css

92 ms

vendor_red_10.css

116 ms

im_component.css

126 ms

alarm_menu.css

114 ms

Our browser made a total of 182 requests to load all elements on the main page. We found that 23% of them (42 requests) were addressed to the original Smamori.jp, 46% (83 requests) were made to Vendor-cdn.imweb.me and 22% (40 requests) were made to Cdn.imweb.me. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Cdn.imweb.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (57%)

Content Size

1.8 MB

After Optimization

765.6 kB

In fact, the total size of Smamori.jp main page is 1.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. Only a small number of websites need less resources to load. HTML takes 985.6 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 874.7 kB

  • Original 985.6 kB
  • After minification 971.4 kB
  • After compression 110.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 874.7 kB or 89% of the original size.

Image Optimization

-72%

Potential reduce by 2.3 kB

  • Original 3.2 kB
  • After minification 902 B

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. Obviously, Smamori needs image optimization as it can save up to 2.3 kB or 72% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-22%

Potential reduce by 119.8 kB

  • Original 548.2 kB
  • After minification 546.6 kB
  • After compression 428.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 119.8 kB or 22% of the original size.

CSS Optimization

-14%

Potential reduce by 38.0 kB

  • Original 263.5 kB
  • After minification 242.2 kB
  • After compression 225.5 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. Smamori.jp needs all CSS files to be minified and compressed as it can save up to 38.0 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 110 (72%)

Requests Now

153

After Optimization

43

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

Accessibility Review

smamori.jp accessibility score

76

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

smamori.jp SEO score

83

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

    JA

  • Encoding

    UTF-8

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