Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    68% of websites

  • 83

    SEO

    Google-friendlier than
    57% of websites

lupicia.co.jp

【LUPICIA】世界のお茶専門店 ルピシア 〜紅茶・緑茶・烏龍茶・ハーブ〜

Page Load Speed

5.9 sec in total

First Response

573 ms

Resources Loaded

5.2 sec

Page Rendered

189 ms

lupicia.co.jp screenshot

About Website

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

ルピシアでは旬の紅茶、緑茶、烏龍茶はもちろん、オリジナルのブレンドティー、フレーバードティーなど、世界中のお茶をご紹介しております。お茶の種類や決まったスタイルにとらわれず、世界に向けて新しい自由なお茶の文化を発信してまいります。おいしいお茶との出合いをどうぞお楽しみください。

Visit lupicia.co.jp

Key Findings

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

Performance Metrics

lupicia.co.jp performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

lupicia.co.jp

573 ms

www.lupicia.com

532 ms

default.aspx

1305 ms

jquery-1.8.2.js

1204 ms

style.css

362 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lupicia.co.jp, 93% (55 requests) were made to Lupicia.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Lupicia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 144.7 kB (15%)

Content Size

936.4 kB

After Optimization

791.8 kB

In fact, the total size of Lupicia.co.jp main page is 936.4 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. Only 10% of websites need less resources to load. Images take 724.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 26.9 kB

  • Original 32.6 kB
  • After minification 19.5 kB
  • After compression 5.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 13.1 kB, which is 40% 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 26.9 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 11.8 kB

  • Original 724.1 kB
  • After minification 712.3 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. LUPICIA images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 98.9 kB

  • Original 170.3 kB
  • After minification 170.0 kB
  • After compression 71.4 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 98.9 kB or 58% of the original size.

CSS Optimization

-75%

Potential reduce by 7.1 kB

  • Original 9.5 kB
  • After minification 7.1 kB
  • After compression 2.4 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. Lupicia.co.jp needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 75% of the original size.

Requests Breakdown

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

Requests Now

56

After Optimization

35

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LUPICIA. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

lupicia.co.jp accessibility score

58

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

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

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

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

lupicia.co.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

Page has valid source maps

SEO Factors

lupicia.co.jp SEO score

83

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

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lupicia.co.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 Lupicia.co.jp 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 LUPICIA. 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: