Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 42

    SEO

    Google-friendlier than
    18% of websites

aikaengei.com

胡蝶蘭専門│生産と花販売の胡蝶蘭生花なら愛華園芸

Page Load Speed

6.3 sec in total

First Response

961 ms

Resources Loaded

4.4 sec

Page Rendered

910 ms

aikaengei.com screenshot

About Website

Welcome to aikaengei.com homepage info - get ready to check Aikaengei best content for Japan right away, or after learning these important things about aikaengei.com

大切に育てた胡蝶蘭をお届けします。愛華園芸は宮崎胡蝶蘭の生産農園です。高品質の苗をまごころ込めて、胡蝶蘭の本当の華やかさを引き出して育てております。

Visit aikaengei.com

Key Findings

We analyzed Aikaengei.com page load time and found that the first response time was 961 ms and then it took 5.3 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

aikaengei.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value1.009

2/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

aikaengei.com

961 ms

main.css

394 ms

sdk.js

268 ms

title5.gif

290 ms

RAN-W55.gif

743 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 55% of them (76 requests) were addressed to the original Aikaengei.com, 26% (35 requests) were made to Static.xx.fbcdn.net and 12% (17 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Aikaengei.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 57.5 kB (3%)

Content Size

2.0 MB

After Optimization

2.0 MB

In fact, the total size of Aikaengei.com main page is 2.0 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. 50% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 54.8 kB

  • Original 66.1 kB
  • After minification 52.9 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 13.2 kB, which is 20% 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 54.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 2.2 kB

  • Original 2.0 MB
  • After minification 2.0 MB

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. Aikaengei images are well optimized though.

CSS Optimization

-65%

Potential reduce by 433 B

  • Original 665 B
  • After minification 548 B
  • After compression 232 B

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. Aikaengei.com needs all CSS files to be minified and compressed as it can save up to 433 B or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (28%)

Requests Now

136

After Optimization

98

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

Accessibility Review

aikaengei.com accessibility score

65

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

aikaengei.com best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

aikaengei.com SEO score

42

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Aikaengei.com 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 Aikaengei.com 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 Aikaengei. 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: