Tools & Wizards About Us
nafeel.jp screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

nafeel.jp

《公式》ウォーターサーバー・宅配水のネイフィールウォーター

Page Load Speed

6.6 sec in total

First Response

625 ms

Resources Loaded

5.6 sec

Page Rendered

370 ms

nafeel.jp screenshot

About Website

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

選べる天然水とウォーターサーバーのネイフィールウォーター公式サイトです。サーバーのレンタル料・配送料も無料でお支払いは「お水料金のみ」です。天然水・ウォーターサーバーのネイフィールウォーター

Visit nafeel.jp

Key Findings

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

Performance Metrics

nafeel.jp performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value2,290 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.548

13/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

nafeel.jp

625 ms

nafeel.jp

835 ms

ytag.js

682 ms

import_pc.css

326 ms

slider-pro.css

491 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 79% of them (74 requests) were addressed to the original Nafeel.jp, 4% (4 requests) were made to Webfonts.sakura.ne.jp and 3% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Nafeel.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 258.9 kB (14%)

Content Size

1.9 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 35.0 kB

  • Original 46.9 kB
  • After minification 44.1 kB
  • After compression 11.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 35.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 4.7 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. Nafeel images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 184.7 kB

  • Original 339.4 kB
  • After minification 337.4 kB
  • After compression 154.7 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 184.7 kB or 54% of the original size.

CSS Optimization

-84%

Potential reduce by 34.6 kB

  • Original 41.3 kB
  • After minification 23.5 kB
  • After compression 6.7 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. Nafeel.jp needs all CSS files to be minified and compressed as it can save up to 34.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (35%)

Requests Now

89

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nafeel.jp

nafeel.jp

625 ms

nafeel.jp

nafeel.jp

835 ms

ytag.js

ytag.js

682 ms

import_pc.css

import_pc.css

326 ms

slider-pro.css

slider-pro.css

491 ms

top.css

top.css

495 ms

copyright.js

copyright.js

505 ms

rollover.js

rollover.js

569 ms

jquery.js

jquery.js

1141 ms

smoothScroll2.js

smoothScroll2.js

648 ms

heightLine.js

heightLine.js

654 ms

jquery.sliderPro.min.js

jquery.sliderPro.min.js

1155 ms

pageTop.js

pageTop.js

668 ms

sakurav3.js

sakurav3.js

1566 ms

analytics.js

analytics.js

758 ms

a8sales.js

a8sales.js

19 ms

a8crossDomain.js

a8crossDomain.js

21 ms

conversion.js

conversion.js

183 ms

cmn_reset.css

cmn_reset.css

539 ms

cmn_style.css

cmn_style.css

494 ms

module.css

module.css

509 ms

print.css

print.css

623 ms

ts

ts

296 ms

js

js

134 ms

bg07.jpg

bg07.jpg

668 ms

logo_header01.gif

logo_header01.gif

177 ms

txt_header01.gif

txt_header01.gif

296 ms

btn_header03.jpg

btn_header03.jpg

295 ms

blank.gif

blank.gif

176 ms

thumb_slider14.jpg

thumb_slider14.jpg

293 ms

thumb_slider01.jpg

thumb_slider01.jpg

368 ms

thumb_slider13.jpg

thumb_slider13.jpg

368 ms

thumb_slider12.jpg

thumb_slider12.jpg

395 ms

thumb_slider05.jpg

thumb_slider05.jpg

395 ms

btn_gNavi01.jpg

btn_gNavi01.jpg

436 ms

btn_gNavi02.jpg

btn_gNavi02.jpg

534 ms

btn_gNavi03.jpg

btn_gNavi03.jpg

534 ms

btn_gNavi04.jpg

btn_gNavi04.jpg

585 ms

btn_gNavi05.jpg

btn_gNavi05.jpg

584 ms

btn_gNavi06.jpg

btn_gNavi06.jpg

652 ms

btn_gNavi07.jpg

btn_gNavi07.jpg

698 ms

thumb_campaign01.jpg

thumb_campaign01.jpg

699 ms

thumb_campaign02.jpg

thumb_campaign02.jpg

773 ms

thumb_campaign03.jpg

thumb_campaign03.jpg

775 ms

thumb_top06.jpg

thumb_top06.jpg

868 ms

thumb_kyo01.jpg

thumb_kyo01.jpg

993 ms

btn_common04.jpg

btn_common04.jpg

863 ms

thumb_hita01.jpg

thumb_hita01.jpg

864 ms

btn_common03.jpg

btn_common03.jpg

962 ms

thumb_fujinonozomi01.jpg

thumb_fujinonozomi01.jpg

964 ms

btn_common05.jpg

btn_common05.jpg

1029 ms

pic_top05.jpg

pic_top05.jpg

1029 ms

ico_top01.jpg

ico_top01.jpg

1083 ms

btn_top01.jpg

btn_top01.jpg

1151 ms

pic_top04.jpg

pic_top04.jpg

1155 ms

ico_top02.jpg

ico_top02.jpg

1157 ms

pic_top06.jpg

pic_top06.jpg

1193 ms

ico_top03.jpg

ico_top03.jpg

1194 ms

ico_top01.png

ico_top01.png

1299 ms

pic_column01.jpg

pic_column01.jpg

1530 ms

sdk.js

sdk.js

124 ms

205 ms

201 ms

sdk.js

sdk.js

152 ms

ts

ts

228 ms

ab.woff

ab.woff

418 ms

pic_column05.jpg

pic_column05.jpg

1174 ms

js

js

71 ms

pic_column04.jpg

pic_column04.jpg

1036 ms

img_top03.png

img_top03.png

1235 ms

bnr_side16.jpg

bnr_side16.jpg

1070 ms

bnr_side17.jpg

bnr_side17.jpg

1223 ms

101 ms

analytics.js

analytics.js

18 ms

62 ms

bnr_side18.jpg

bnr_side18.jpg

1124 ms

bnr_side06.jpg

bnr_side06.jpg

1173 ms

collect

collect

15 ms

bnr_side21.gif

bnr_side21.gif

1134 ms

bnr_top11.gif

bnr_top11.gif

1261 ms

collect

collect

27 ms

ga-audiences

ga-audiences

15 ms

logo_footer01.gif

logo_footer01.gif

1299 ms

bnr_footerPerson01.jpg

bnr_footerPerson01.jpg

1158 ms

bnr_footerBusiness01.jpg

bnr_footerBusiness01.jpg

1159 ms

bg04.gif

bg04.gif

1141 ms

h3_top01.jpg

h3_top01.jpg

1146 ms

bg_side01.jpg

bg_side01.jpg

1168 ms

ico_footer01.gif

ico_footer01.gif

1193 ms

ico_pageTop01.png

ico_pageTop01.png

1159 ms

openhand.cur

openhand.cur

1214 ms

img_slider10.jpg

img_slider10.jpg

1905 ms

img_slider14.jpg

img_slider14.jpg

1607 ms

img_slider06.jpg

img_slider06.jpg

1612 ms

Accessibility Review

nafeel.jp accessibility score

77

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

[role]s do not have all required [aria-*] attributes

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

nafeel.jp best practices score

75

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

Page has valid source maps

SEO Factors

nafeel.jp SEO score

79

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

    N/A

  • Encoding

    UTF-8

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

nafeel.jp

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