Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

suguki-narita.com

京都の漬物なら京つけもの御すぐき處京都なり田

Page Load Speed

9.3 sec in total

First Response

1.1 sec

Resources Loaded

8 sec

Page Rendered

195 ms

suguki-narita.com screenshot

About Website

Visit suguki-narita.com now to see the best up-to-date Suguki Narita content for Japan and also check out these interesting facts you probably never knew about suguki-narita.com

京都の漬物なら1804年(文化元年)創業の御すぐき處京都なり田。職人が丹念に漬けこんだすぐき、千枚漬、しば漬などの京つけものをお届けします。お歳暮やお中元にもどうぞ。

Visit suguki-narita.com

Key Findings

We analyzed Suguki-narita.com page load time and found that the first response time was 1.1 sec and then it took 8.2 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

suguki-narita.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.314

37/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

suguki-narita.com

1138 ms

default.css

519 ms

common.css

532 ms

home.css

576 ms

jsearch.css

535 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 86% of them (59 requests) were addressed to the original Suguki-narita.com, 6% (4 requests) were made to Google-analytics.com and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Suguki-narita.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 128.9 kB (8%)

Content Size

1.7 MB

After Optimization

1.5 MB

In fact, the total size of Suguki-narita.com main page is 1.7 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. 35% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 13.7 kB

  • Original 18.7 kB
  • After minification 15.5 kB
  • After compression 5.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 3.2 kB, which is 17% 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 13.7 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 5.9 kB

  • Original 1.4 MB
  • After minification 1.4 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. Suguki Narita images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 80.1 kB

  • Original 167.9 kB
  • After minification 166.3 kB
  • After compression 87.9 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 80.1 kB or 48% of the original size.

CSS Optimization

-82%

Potential reduce by 29.2 kB

  • Original 35.7 kB
  • After minification 23.0 kB
  • After compression 6.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. Suguki-narita.com needs all CSS files to be minified and compressed as it can save up to 29.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (29%)

Requests Now

66

After Optimization

47

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

Accessibility Review

suguki-narita.com accessibility score

64

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

suguki-narita.com best practices score

58

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

suguki-narita.com 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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    WINDOWS-31J

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Suguki-narita.com 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 Suguki-narita.com main page’s claimed encoding is windows-31j. 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 Suguki Narita. 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: