Tools & Wizards About Us
nilax.jp screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

nilax.jp

ニラックス株式会社(NILAX)|オフィシャルサイト

Page Load Speed

4.3 sec in total

First Response

723 ms

Resources Loaded

3.4 sec

Page Rendered

185 ms

nilax.jp screenshot

About Website

Visit nilax.jp now to see the best up-to-date NILAX content for Japan and also check out these interesting facts you probably never knew about nilax.jp

ニラックスは、しゃぶしゃぶからオシャレなブッフェレストラン、フードコート、和食まで全国で展開中。

Visit nilax.jp

Key Findings

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

Performance Metrics

nilax.jp performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.372

28/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

nilax.jp

723 ms

import.css

337 ms

top.css

508 ms

jquery.js

696 ms

jquery.plugin.js

519 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 98% of them (64 requests) were addressed to the original Nilax.jp, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Nilax.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 325.0 kB (20%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 21.9 kB

  • Original 26.9 kB
  • After minification 23.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.4 kB, which is 13% 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 21.9 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 69.3 kB

  • Original 1.3 MB
  • After minification 1.2 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. NILAX images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 126.7 kB

  • Original 175.1 kB
  • After minification 148.3 kB
  • After compression 48.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 126.7 kB or 72% of the original size.

CSS Optimization

-87%

Potential reduce by 107.1 kB

  • Original 123.7 kB
  • After minification 92.2 kB
  • After compression 16.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. Nilax.jp needs all CSS files to be minified and compressed as it can save up to 107.1 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (14%)

Requests Now

63

After Optimization

54

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nilax.jp

nilax.jp

723 ms

import.css

import.css

337 ms

top.css

top.css

508 ms

jquery.js

jquery.js

696 ms

jquery.plugin.js

jquery.plugin.js

519 ms

common.js

common.js

696 ms

top.js

top.js

350 ms

analytics.js

analytics.js

505 ms

base.css

base.css

189 ms

layout.css

layout.css

504 ms

contents.css

contents.css

510 ms

js

js

131 ms

com_sp01.png

com_sp01.png

356 ms

index_bg02.png

index_bg02.png

177 ms

8d294b46a319d676da6bbabc0621e7b2.jpg

8d294b46a319d676da6bbabc0621e7b2.jpg

709 ms

9fa8ff3a0982884636118b4c436fbc8f.jpg

9fa8ff3a0982884636118b4c436fbc8f.jpg

513 ms

1a37226d2b34dfcef044d958eecd098c.jpg

1a37226d2b34dfcef044d958eecd098c.jpg

532 ms

2a3383096e54b36fd95552db65cf0aee.png

2a3383096e54b36fd95552db65cf0aee.png

352 ms

b8afebcc1a9ef891b66c4db1463b1f74.jpg

b8afebcc1a9ef891b66c4db1463b1f74.jpg

685 ms

index_bg01.png

index_bg01.png

525 ms

index_tx02.png

index_tx02.png

532 ms

brand03_logo01.png

brand03_logo01.png

680 ms

brand08_logo01.png

brand08_logo01.png

698 ms

NewMarrket_logo_fix.jpg

NewMarrket_logo_fix.jpg

708 ms

brand34_logo01.png

brand34_logo01.png

706 ms

97d510174bffd37fde691dce30549048.png

97d510174bffd37fde691dce30549048.png

849 ms

e93a63a1cfd1a6316cd29ca53798404e.png

e93a63a1cfd1a6316cd29ca53798404e.png

856 ms

brand04_logo01.png

brand04_logo01.png

871 ms

c78476a3f24e23be3ebc89358c483645_1.png

c78476a3f24e23be3ebc89358c483645_1.png

881 ms

brand25_logo01.png

brand25_logo01.png

882 ms

exbluethebuffet_logo.png

exbluethebuffet_logo.png

882 ms

brand10_logo01.png

brand10_logo01.png

1017 ms

brand09_logo01.png

brand09_logo01.png

1024 ms

brand14_logo01.png

brand14_logo01.png

1044 ms

brand17_logo01.png

brand17_logo01.png

1055 ms

kushiyo_logo.png

kushiyo_logo.png

1057 ms

tetote180420.png

tetote180420.png

1058 ms

logo_the_garden.png

logo_the_garden.png

1185 ms

brand23_logo01.png

brand23_logo01.png

1193 ms

brand24_logo01.png

brand24_logo01.png

1217 ms

brand19_logo01.png

brand19_logo01.png

1231 ms

brand32_logo01.png

brand32_logo01.png

1231 ms

logo_suupu.png

logo_suupu.png

1232 ms

ab32796d51f822646d41a3bfb16c72fe.png

ab32796d51f822646d41a3bfb16c72fe.png

1352 ms

b2c5aa2f3f83e394f83a1def9a8ed6dc.jpg

b2c5aa2f3f83e394f83a1def9a8ed6dc.jpg

1362 ms

brand37_logo01.png

brand37_logo01.png

1389 ms

brand38_logo01.png

brand38_logo01.png

1404 ms

brand40_logo01.png

brand40_logo01.png

1406 ms

brand27_logo01.png

brand27_logo01.png

1234 ms

brand_logo3.jpg

brand_logo3.jpg

1173 ms

f2fddc9f5c0ebca5e4af8cbeeaaeeb92_1.png

f2fddc9f5c0ebca5e4af8cbeeaaeeb92_1.png

1181 ms

index_bg03.png

index_bg03.png

1055 ms

com_sp02.png

com_sp02.png

1056 ms

index_tx03.png

index_tx03.png

1054 ms

brand00_logo01.png

brand00_logo01.png

1054 ms

index_tx04.png

index_tx04.png

1013 ms

com_bn12.png

com_bn12.png

1020 ms

com_bn04.png

com_bn04.png

1041 ms

com_bn01.png

com_bn01.png

1049 ms

com_bn07.png

com_bn07.png

1054 ms

com_bn08.png

com_bn08.png

1053 ms

index_bn01.png

index_bn01.png

1011 ms

index_bn02.png

index_bn02.png

1018 ms

index_bn03.png

index_bn03.png

1041 ms

com_bn04.jpg

com_bn04.jpg

1050 ms

Accessibility Review

nilax.jp accessibility score

92

Accessibility Issues

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.

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

Links do not have a discernible name

Best Practices

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

SEO Factors

nilax.jp SEO score

82

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

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 doesn't use 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 Nilax.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 Nilax.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

nilax.jp

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