Report Summary

  • 23

    Performance

    Renders faster than
    43% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 70% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

applemango.jp

【産地直送!】沖縄宮古島産完熟アップルマンゴー| マンゴー屋さん | マンゴー屋さん

Page Load Speed

9.2 sec in total

First Response

937 ms

Resources Loaded

7.8 sec

Page Rendered

513 ms

applemango.jp screenshot

About Website

Click here to check amazing Applemango content. Otherwise, check out these important facts you probably never knew about applemango.jp

沖縄宮古島産完熟アップルマンゴーを産地直送!今年も夏の贅沢をお届けします。甘い蜜、フレッシュな香り、なめらかな食感。こだわりのアップルマンゴーをぜひ花咲カットで。贈り物には「美麗品」、ご家庭や切り分けて提供する場合には「ご家庭・お徳用」がおすすめです。

Visit applemango.jp

Key Findings

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

Performance Metrics

applemango.jp performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

applemango.jp

937 ms

m_sys_common.css

338 ms

import.css

342 ms

script.js

346 ms

jquery.min.js

33 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 24% of them (16 requests) were addressed to the original Applemango.jp, 27% (18 requests) were made to Gigaplus.makeshop.jp and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Applemango.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 423.9 kB (31%)

Content Size

1.4 MB

After Optimization

943.0 kB

In fact, the total size of Applemango.jp main page is 1.4 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. 45% of websites need less resources to load. Images take 790.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 22.6 kB

  • Original 29.9 kB
  • After minification 28.2 kB
  • After compression 7.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 22.6 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 3.2 kB

  • Original 790.5 kB
  • After minification 787.2 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. Applemango images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 141.7 kB

  • Original 238.4 kB
  • After minification 235.9 kB
  • After compression 96.6 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 141.7 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 256.3 kB

  • Original 308.1 kB
  • After minification 286.2 kB
  • After compression 51.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. Applemango.jp needs all CSS files to be minified and compressed as it can save up to 256.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (66%)

Requests Now

62

After Optimization

21

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

Accessibility Review

applemango.jp accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role] values are not valid

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

Links do not have a discernible name

Best Practices

applemango.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

applemango.jp SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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 Applemango.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 Applemango.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 Applemango. 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: