Report Summary

  • 0

    Performance

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 0

    Best Practices

  • 50

    SEO

    Google-friendlier than
    18% of websites

amora.jp

Amora - A sua loja de calçados brasileiros no Japão – AMORA

Page Load Speed

8.2 sec in total

First Response

1.3 sec

Resources Loaded

6.7 sec

Page Rendered

242 ms

About Website

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

AMORA é um E-commerce com sede em Iwata - Japão, que nasceu com o objetivo de trazer o melhor da moda brasileira para o Japão.

Visit amora.jp

Key Findings

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

Performance Metrics

amora.jp performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value17.0 s

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value14,330 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.738

6/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

amora.jp

1284 ms

bootstrap.css

1687 ms

stylesheet.css

1367 ms

css

56 ms

font.css

895 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 64% of them (93 requests) were addressed to the original Amora.jp, 10% (15 requests) were made to Scontent-iad3-1.xx.fbcdn.net and 5% (7 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Amora.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 724.6 kB (13%)

Content Size

5.5 MB

After Optimization

4.8 MB

In fact, the total size of Amora.jp main page is 5.5 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. 70% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 87.5 kB

  • Original 101.2 kB
  • After minification 77.9 kB
  • After compression 13.7 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 23.3 kB, which is 23% 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 87.5 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 43.7 kB

  • Original 4.6 MB
  • After minification 4.6 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. Amora images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 341.1 kB

  • Original 515.3 kB
  • After minification 509.9 kB
  • After compression 174.3 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 341.1 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 252.3 kB

  • Original 298.3 kB
  • After minification 244.4 kB
  • After compression 45.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. Amora.jp needs all CSS files to be minified and compressed as it can save up to 252.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (48%)

Requests Now

134

After Optimization

70

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

Accessibility Review

amora.jp accessibility score

63

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

Document doesn't have a <title> element

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 [lang] attribute

SEO Factors

amora.jp SEO score

50

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Open Graph data is detected on the main page of Amora. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: