Report Summary

  • 0

    Performance

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

nosmoke55.jp

日本禁煙学会

Page Load Speed

6.8 sec in total

First Response

767 ms

Resources Loaded

3.5 sec

Page Rendered

2.5 sec

nosmoke55.jp screenshot

About Website

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

一般社団法人 日本禁煙学会の公式ホームページです

Visit nosmoke55.jp

Key Findings

We analyzed Nosmoke55.jp page load time and found that the first response time was 767 ms and then it took 6 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

nosmoke55.jp performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

nosmoke55.jp

767 ms

title.html

707 ms

menu.html

722 ms

top.html

1310 ms

table.css

204 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 88% of them (63 requests) were addressed to the original Nosmoke55.jp, 4% (3 requests) were made to S.ytimg.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Notobacco.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 349.7 kB (74%)

Content Size

474.8 kB

After Optimization

125.1 kB

In fact, the total size of Nosmoke55.jp main page is 474.8 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. 35% of websites need less resources to load. CSS take 246.7 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 6.4 kB

  • Original 10.0 kB
  • After minification 9.0 kB
  • After compression 3.7 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. This page needs HTML code to be minified as it can gain 1.1 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 6.4 kB or 64% of the original size.

Image Optimization

-13%

Potential reduce by 749 B

  • Original 5.6 kB
  • After minification 4.9 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. Obviously, Nosmoke 55 needs image optimization as it can save up to 749 B or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 137.6 kB

  • Original 212.4 kB
  • After minification 212.3 kB
  • After compression 74.8 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 137.6 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 204.9 kB

  • Original 246.7 kB
  • After minification 246.2 kB
  • After compression 41.8 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. Nosmoke55.jp needs all CSS files to be minified and compressed as it can save up to 204.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (30%)

Requests Now

69

After Optimization

48

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

Accessibility Review

nosmoke55.jp accessibility score

100

Accessibility Issues

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nosmoke55.jp SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nosmoke55.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 Nosmoke55.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Nosmoke 55. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: