Tools & Wizards About Us
nakago.com screenshot

Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

nakago.com

NAKAGO 中合

Page Load Speed

2.2 sec in total

First Response

46 ms

Resources Loaded

2.1 sec

Page Rendered

81 ms

nakago.com screenshot

About Website

Click here to check amazing NAKAGO content for Japan. Otherwise, check out these important facts you probably never knew about nakago.com

福島県福島市の百貨店、中合。『この街と人が好きだから』をコンセプトに地域に密着した催事・イベントの最新情報をお届けします。

Visit nakago.com

Key Findings

We analyzed Nakago.com page load time and found that the first response time was 46 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

nakago.com performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

nakago.com

46 ms

nakago.com

656 ms

reset.css

643 ms

common_layout.css

738 ms

style.css

684 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 70% of them (7 requests) were addressed to the original Nakago.com, 20% (2 requests) were made to Ssl.google-analytics.com and 10% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (738 ms) belongs to the original domain Nakago.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.4 kB (5%)

Content Size

64.7 kB

After Optimization

61.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nakago.com main page is 64.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 47.2 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 2.3 kB

  • Original 4.0 kB
  • After minification 3.3 kB
  • After compression 1.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 734 B, which is 18% 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 2.3 kB or 58% of the original size.

Image Optimization

-2%

Potential reduce by 239 B

  • Original 10.8 kB
  • After minification 10.5 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. NAKAGO images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 47.2 kB
  • After minification 47.2 kB
  • After compression 47.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. This website has mostly compressed JavaScripts.

CSS Optimization

-30%

Potential reduce by 805 B

  • Original 2.7 kB
  • After minification 2.7 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. Nakago.com needs all CSS files to be minified and compressed as it can save up to 805 B or 30% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NAKAGO. According to our analytics all requests are already optimized.

Network Requests Diagram

nakago.com

nakago.com

46 ms

nakago.com

nakago.com

656 ms

reset.css

reset.css

643 ms

common_layout.css

common_layout.css

738 ms

style.css

style.css

684 ms

jquery.min.js

jquery.min.js

21 ms

ga.js

ga.js

38 ms

hd_message.png

hd_message.png

639 ms

hd_logo.png

hd_logo.png

642 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

nakago.com accessibility score

75

Accessibility Issues

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

nakago.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

nakago.com SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nakago.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nakago.com 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

nakago.com

Open Graph description is not detected on the main page of NAKAGO. 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: