Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

awn.jp

経営コンサルタント 岡本吏郎 ビジネスサポートあうん

Page Load Speed

8.2 sec in total

First Response

867 ms

Resources Loaded

7 sec

Page Rendered

340 ms

awn.jp screenshot

About Website

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

最近は、リアリズム(現実主義)の人気がまったくありません。「こうしたら儲かる」という幻想の方が大人気。でも、そんな時だからこそチャンスです。私たちは、リアル思考で稼ぎ続けましょう。

Visit awn.jp

Key Findings

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

awn.jp performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.233

53/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

awn.jp

867 ms

base.css

334 ms

mainmenu.css

339 ms

index.css

347 ms

top.js

354 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 80% of them (80 requests) were addressed to the original Awn.jp, 3% (3 requests) were made to Ura.awn.jp and 2% (2 requests) were made to Ws.amazon.co.jp. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Awn.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 397.8 kB (43%)

Content Size

925.0 kB

After Optimization

527.2 kB

In fact, the total size of Awn.jp main page is 925.0 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. 55% of websites need less resources to load. Javascripts take 494.1 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 14.8 kB

  • Original 21.0 kB
  • After minification 20.6 kB
  • After compression 6.3 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 14.8 kB or 70% of the original size.

Image Optimization

-6%

Potential reduce by 19.7 kB

  • Original 357.4 kB
  • After minification 337.7 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. Awn images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 321.8 kB

  • Original 494.1 kB
  • After minification 349.5 kB
  • After compression 172.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 321.8 kB or 65% of the original size.

CSS Optimization

-79%

Potential reduce by 41.5 kB

  • Original 52.4 kB
  • After minification 37.2 kB
  • After compression 10.9 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. Awn.jp needs all CSS files to be minified and compressed as it can save up to 41.5 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

98

After Optimization

50

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

Accessibility Review

awn.jp accessibility score

94

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

Best Practices

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

SEO Factors

awn.jp SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Awn.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 Awn.jp main page’s claimed encoding is euc-jp. 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 Awn. 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: