Tools & Wizards About Us
awe.jp screenshot

Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

awe.jp

DOMAIN ERROR

Page Load Speed

5.1 sec in total

First Response

591 ms

Resources Loaded

4.3 sec

Page Rendered

226 ms

awe.jp screenshot

About Website

Click here to check amazing Awe content for Japan. Otherwise, check out these important facts you probably never knew about awe.jp

Visit awe.jp

Key Findings

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

Performance Metrics

awe.jp performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value340 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.115

86/100

15%

TTI (Time to Interactive)

Value4.0 s

87/100

10%

Network Requests Diagram

awe.jp

591 ms

style.css

319 ms

jquery.min.js

1324 ms

jquery.fittext.js

374 ms

tokyo_tower.jpg

3416 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 63% of them (5 requests) were addressed to the original Awe.jp, 25% (2 requests) were made to Google-analytics.com and 13% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Awe.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 166.5 kB (17%)

Content Size

979.4 kB

After Optimization

812.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Awe.jp main page is 979.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 717.6 kB which makes up the majority of the site volume.

HTML Optimization

-55%

Potential reduce by 1.3 kB

  • Original 2.3 kB
  • After minification 2.1 kB
  • After compression 1.1 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 245 B, 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 1.3 kB or 55% of the original size.

Image Optimization

-0%

Potential reduce by 863 B

  • Original 717.6 kB
  • After minification 716.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. Awe images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 159.2 kB

  • Original 253.0 kB
  • After minification 252.5 kB
  • After compression 93.7 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 159.2 kB or 63% of the original size.

CSS Optimization

-78%

Potential reduce by 5.1 kB

  • Original 6.5 kB
  • After minification 5.3 kB
  • After compression 1.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. Awe.jp needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Awe. According to our analytics all requests are already optimized.

Network Requests Diagram

awe.jp

awe.jp

591 ms

style.css

style.css

319 ms

jquery.min.js

jquery.min.js

1324 ms

jquery.fittext.js

jquery.fittext.js

374 ms

tokyo_tower.jpg

tokyo_tower.jpg

3416 ms

analytics.js

analytics.js

8 ms

collect

collect

13 ms

collect

collect

57 ms

Accessibility Review

awe.jp accessibility score

68

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 valid value for its [lang] attribute.

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

awe.jp best practices score

83

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

awe.jp SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    JP

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Awe.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed language. Our system also found out that Awe.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

awe.jp

Open Graph description is not detected on the main page of Awe. 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: