Tools & Wizards About Us
nogami-p-hotel.jp screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

nogami-p-hotel.jp

のがみプレジデントホテル | 福岡県飯塚市

Page Load Speed

11.4 sec in total

First Response

1.5 sec

Resources Loaded

9.5 sec

Page Rendered

423 ms

nogami-p-hotel.jp screenshot

About Website

Welcome to nogami-p-hotel.jp homepage info - get ready to check Nogami P Hotel best content right away, or after learning these important things about nogami-p-hotel.jp

福岡県　飯塚市。のがみプレジデントホテル。ご宿泊・ブライダル・ご宴会・レストランはもちろんシェフ自慢の料理を取り揃え、好みに合わせて出張パーティ承ります。

Visit nogami-p-hotel.jp

Key Findings

We analyzed Nogami-p-hotel.jp page load time and found that the first response time was 1.5 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

nogami-p-hotel.jp performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value21.0 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

nogami-p-hotel.jp

1497 ms

bgdposobject.css

344 ms

common.css

542 ms

slimbox2.css

374 ms

utilities.js

374 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 97% of them (91 requests) were addressed to the original Nogami-p-hotel.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Www2.489ban.net. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Nogami-p-hotel.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 941.7 kB (16%)

Content Size

5.8 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nogami-p-hotel.jp main page is 5.8 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. 30% of websites need less resources to load. Images take 5.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 54.1 kB

  • Original 64.8 kB
  • After minification 55.1 kB
  • After compression 10.6 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 9.7 kB, which is 15% 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 54.1 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 252.9 kB

  • Original 5.0 MB
  • After minification 4.7 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. Nogami P Hotel images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 627.8 kB

  • Original 768.2 kB
  • After minification 487.7 kB
  • After compression 140.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 627.8 kB or 82% of the original size.

CSS Optimization

-81%

Potential reduce by 6.8 kB

  • Original 8.5 kB
  • After minification 6.3 kB
  • After compression 1.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. Nogami-p-hotel.jp needs all CSS files to be minified and compressed as it can save up to 6.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (12%)

Requests Now

93

After Optimization

82

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nogami-p-hotel.jp

nogami-p-hotel.jp

1497 ms

bgdposobject.css

bgdposobject.css

344 ms

common.css

common.css

542 ms

slimbox2.css

slimbox2.css

374 ms

utilities.js

utilities.js

374 ms

common.js

common.js

383 ms

jquery-1.9.1.js

jquery-1.9.1.js

1740 ms

jquery-ui-1.10.1.custom.js

jquery-ui-1.10.1.custom.js

2416 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

746 ms

jquery.backgroundpos.min.js

jquery.backgroundpos.min.js

573 ms

slimbox2.js

slimbox2.js

721 ms

bgdissolveobject.js

bgdissolveobject.js

955 ms

bgdtsliderobject2.js

bgdtsliderobject2.js

1083 ms

bgdposobject.js

bgdposobject.js

920 ms

nogami

nogami

651 ms

analytics.js

analytics.js

23 ms

headlogo.png

headlogo.png

744 ms

navisep.png

navisep.png

346 ms

navi01.png

navi01.png

346 ms

navi02.png

navi02.png

355 ms

navi03.png

navi03.png

356 ms

navi04.png

navi04.png

364 ms

headtel.png

headtel.png

680 ms

fbbtn.png

fbbtn.png

513 ms

mbtn01.png

mbtn01.png

531 ms

mbtn02.png

mbtn02.png

533 ms

mbtn03.png

mbtn03.png

545 ms

mbtn04.png

mbtn04.png

683 ms

mbtn05.png

mbtn05.png

706 ms

headolbtn.png

headolbtn.png

710 ms

headtoibtn.png

headtoibtn.png

906 ms

hshousaibtn.png

hshousaibtn.png

1016 ms

arrow_l.png

arrow_l.png

852 ms

arrow_r.png

arrow_r.png

882 ms

hscompname.png

hscompname.png

886 ms

midbg.png

midbg.png

915 ms

headsep.png

headsep.png

1022 ms

platebg_newtopics.png

platebg_newtopics.png

1058 ms

st_newtopics.png

st_newtopics.png

1064 ms

il_rss.png

il_rss.png

1085 ms

il_newtopics.png

il_newtopics.png

1102 ms

tabline.png

tabline.png

1183 ms

tab01.png

tab01.png

1191 ms

tab02.png

tab02.png

1234 ms

tab03.png

tab03.png

1239 ms

tab04.png

tab04.png

1265 ms

tab05.png

tab05.png

1286 ms

tab06.png

tab06.png

1353 ms

platebg_plansearch.png

platebg_plansearch.png

1360 ms

st_plansearch.png

st_plansearch.png

1409 ms

%EF%BD%8B%EF%BD%8B%EF%BD%8B%EF%BD%8B-112x75.jpg

%EF%BD%8B%EF%BD%8B%EF%BD%8B%EF%BD%8B-112x75.jpg

1416 ms

%E4%BD%9C%E5%85%B5%E8%A1%9B%E5%B1%95%E5%91%8A%E7%9F%A5%E3%83%90%E3%83%8A%E3%83%BC-112x75.jpg

%E4%BD%9C%E5%85%B5%E8%A1%9B%E5%B1%95%E5%91%8A%E7%9F%A5%E3%83%90%E3%83%8A%E3%83%BC-112x75.jpg

1625 ms

collect

collect

13 ms

2017%E6%8C%AF%E8%A2%96%E5%B1%95%E7%A4%BA%E4%BC%9A-%E7%B8%A6-e1454569035979-112x75.jpg

2017%E6%8C%AF%E8%A2%96%E5%B1%95%E7%A4%BA%E4%BC%9A-%E7%B8%A6-e1454569035979-112x75.jpg

1322 ms

yoyakubtn.png

yoyakubtn.png

1358 ms

bbanner01.png

bbanner01.png

2381 ms

bbanner06.png

bbanner06.png

2477 ms

rbanner01.png

rbanner01.png

1636 ms

rbanner02.png

rbanner02.png

1706 ms

rbanner03.png

rbanner03.png

1879 ms

rbanner04.png

rbanner04.png

1848 ms

spbanner_gt.png

spbanner_gt.png

1632 ms

st_ichioshi.png

st_ichioshi.png

1678 ms

%EF%BD%8B%EF%BD%8B%EF%BD%8B%EF%BD%8B-181x256.jpg

%EF%BD%8B%EF%BD%8B%EF%BD%8B%EF%BD%8B-181x256.jpg

2088 ms

IMG_9828-190x127.jpg

IMG_9828-190x127.jpg

2004 ms

%E4%B8%89%E9%81%8A%E4%BA%AD%E5%A5%BD%E6%A5%BD1-190x127.jpg

%E4%B8%89%E9%81%8A%E4%BA%AD%E5%A5%BD%E6%A5%BD1-190x127.jpg

1840 ms

planlistbtn.png

planlistbtn.png

1864 ms

st_info.png

st_info.png

1867 ms

eventlistbtn.png

eventlistbtn.png

1898 ms

rtt01.png

rtt01.png

2001 ms

midlogo.png

midlogo.png

2155 ms

fmisep.png

fmisep.png

1986 ms

fmi01.png

fmi01.png

1932 ms

fmi02.png

fmi02.png

1943 ms

fmi03.png

fmi03.png

1947 ms

fmi04.png

fmi04.png

2002 ms

fmi05.png

fmi05.png

1987 ms

fmi06.png

fmi06.png

2024 ms

fmi07.png

fmi07.png

1966 ms

fmi08.png

fmi08.png

1990 ms

fmi09.png

fmi09.png

1993 ms

footsep.png

footsep.png

2002 ms

footlogo.png

footlogo.png

1975 ms

footinfo01.png

footinfo01.png

2202 ms

footcopy.png

footcopy.png

1982 ms

photo01.png

photo01.png

3234 ms

photo04_s.png

photo04_s.png

2494 ms

photo01_s.png

photo01_s.png

2541 ms

photo03_04_s.png

photo03_04_s.png

2323 ms

photo02_s.png

photo02_s.png

2791 ms

dot01.png

dot01.png

1978 ms

photo03_04.png

photo03_04.png

4043 ms

photo02.png

photo02.png

3436 ms

photo04.png

photo04.png

4052 ms

Accessibility Review

nogami-p-hotel.jp accessibility score

77

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

nogami-p-hotel.jp best practices score

67

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

SEO Factors

nogami-p-hotel.jp SEO score

54

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

High

robots.txt is not valid

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

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 Nogami-p-hotel.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 Nogami-p-hotel.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

nogami-p-hotel.jp

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