Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

amphora.jp

amphora / TOPページ

Page Load Speed

3.8 sec in total

First Response

572 ms

Resources Loaded

2.8 sec

Page Rendered

433 ms

amphora.jp screenshot

About Website

Welcome to amphora.jp homepage info - get ready to check Amphora best content right away, or after learning these important things about amphora.jp

アンフォラ オリエンタルジュエリー・セレクトショップ

Visit amphora.jp

Key Findings

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

Performance Metrics

amphora.jp performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value30.4 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.541

14/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

amphora.jp

572 ms

flash_activate.js

177 ms

stylesheet.css

317 ms

trustlogo.js

35 ms

trustlogo.js

71 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 77% of them (55 requests) were addressed to the original Amphora.jp, 8% (6 requests) were made to Trustlogo.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Amphora.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 106.5 kB (11%)

Content Size

990.3 kB

After Optimization

883.8 kB

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

HTML Optimization

-82%

Potential reduce by 32.3 kB

  • Original 39.3 kB
  • After minification 35.2 kB
  • After compression 7.0 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 4.1 kB, 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 32.3 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 38.1 kB

  • Original 896.9 kB
  • After minification 858.8 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. Amphora images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 25.1 kB

  • Original 41.1 kB
  • After minification 39.7 kB
  • After compression 16.1 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 25.1 kB or 61% of the original size.

CSS Optimization

-85%

Potential reduce by 11.1 kB

  • Original 13.0 kB
  • After minification 8.3 kB
  • After compression 1.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. Amphora.jp needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (13%)

Requests Now

67

After Optimization

58

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

Accessibility Review

amphora.jp accessibility score

76

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

[aria-hidden="true"] elements contain focusable descendents

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

amphora.jp best practices score

75

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

Page has valid source maps

SEO Factors

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

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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