Tools & Wizards About Us
aene.jp screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

aene.jp

aene.jp – このドメインはお名前.comで取得されています。

Page Load Speed

2.4 sec in total

First Response

391 ms

Resources Loaded

1.7 sec

Page Rendered

328 ms

aene.jp screenshot

About Website

Visit aene.jp now to see the best up-to-date Aene content and also check out these interesting facts you probably never knew about aene.jp

高級な美容ドリンクだからこそ正確な情報を大切に。美容ドリンクをランキングで紹介します。

Visit aene.jp

Key Findings

We analyzed Aene.jp page load time and found that the first response time was 391 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

aene.jp performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.177

68/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

aene.jp

391 ms

styles.css

222 ms

bnr.gif

470 ms

2nd_gets.php

502 ms

top.gif

325 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 85% of them (17 requests) were addressed to the original Aene.jp, 5% (1 request) were made to Image.korekara-cfd.com and 5% (1 request) were made to Ac.i2i.jp. The less responsive or slowest element that took the longest time to load (754 ms) belongs to the original domain Aene.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.4 kB (76%)

Content Size

54.4 kB

After Optimization

13.0 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-63%

Potential reduce by 7.1 kB

  • Original 11.2 kB
  • After minification 11.0 kB
  • After compression 4.2 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 7.1 kB or 63% of the original size.

JavaScript Optimization

-71%

Potential reduce by 8.1 kB

  • Original 11.3 kB
  • After minification 9.8 kB
  • After compression 3.2 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 8.1 kB or 71% of the original size.

CSS Optimization

-82%

Potential reduce by 26.2 kB

  • Original 31.9 kB
  • After minification 25.0 kB
  • After compression 5.6 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. Aene.jp needs all CSS files to be minified and compressed as it can save up to 26.2 kB or 82% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aene.jp

aene.jp

391 ms

styles.css

styles.css

222 ms

bnr.gif

bnr.gif

470 ms

2nd_gets.php

2nd_gets.php

502 ms

top.gif

top.gif

325 ms

h_t.gif

h_t.gif

219 ms

o.gif

o.gif

222 ms

h_1.gif

h_1.gif

449 ms

h_2.gif

h_2.gif

449 ms

b_t.gif

b_t.gif

328 ms

b_1.gif

b_1.gif

550 ms

b_2.gif

b_2.gif

554 ms

a_t.gif

a_t.gif

432 ms

a_1.gif

a_1.gif

653 ms

a_2.gif

a_2.gif

754 ms

f.gif

f.gif

560 ms

tables.css

tables.css

343 ms

commonstyles.css

commonstyles.css

443 ms

2014081231385.gif

2014081231385.gif

296 ms

header.gif

header.gif

112 ms

Accessibility Review

aene.jp accessibility score

95

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

Best Practices

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

High

Page has valid source maps

SEO Factors

aene.jp SEO score

85

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

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aene.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 Aene.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

aene.jp

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