Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

genoa.jp

ゼノア化粧料通販・花咲

Page Load Speed

16.2 sec in total

First Response

520 ms

Resources Loaded

15.2 sec

Page Rendered

445 ms

genoa.jp screenshot

About Website

Welcome to genoa.jp homepage info - get ready to check Genoa best content for Japan right away, or after learning these important things about genoa.jp

ゼノア化粧料・ゼノア化粧品の専門販社。Webや電話、Fax等による無料カウンセリングも受付ける

Visit genoa.jp

Key Findings

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

Performance Metrics

genoa.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value36.6 s

0/100

25%

SI (Speed Index)

Value17.3 s

0/100

10%

TBT (Total Blocking Time)

Value670 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

Network Requests Diagram

genoa.jp

520 ms

www.genoa.jp

1128 ms

import_genoa.css

376 ms

css.js

371 ms

navi.js

367 ms

Our browser made a total of 213 requests to load all elements on the main page. We found that 94% of them (200 requests) were addressed to the original Genoa.jp, 2% (4 requests) were made to Google-analytics.com and 1% (3 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Genoa.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 630.7 kB (45%)

Content Size

1.4 MB

After Optimization

771.1 kB

In fact, the total size of Genoa.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. 50% of websites need less resources to load. Images take 687.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 73.8 kB

  • Original 86.7 kB
  • After minification 61.7 kB
  • After compression 12.9 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 25.0 kB, which is 29% 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 73.8 kB or 85% of the original size.

Image Optimization

-11%

Potential reduce by 75.5 kB

  • Original 687.3 kB
  • After minification 611.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. Obviously, Genoa needs image optimization as it can save up to 75.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 148.1 kB

  • Original 250.9 kB
  • After minification 228.7 kB
  • After compression 102.8 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 148.1 kB or 59% of the original size.

CSS Optimization

-88%

Potential reduce by 333.3 kB

  • Original 376.9 kB
  • After minification 267.4 kB
  • After compression 43.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. Genoa.jp needs all CSS files to be minified and compressed as it can save up to 333.3 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

209

After Optimization

123

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

Accessibility Review

genoa.jp accessibility score

66

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-*] attributes do not match their roles

High

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

genoa.jp SEO score

90

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Genoa.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 Genoa.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 description is not detected on the main page of Genoa. 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: