Tools & Wizards About Us
nogeya.jp screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

nogeya.jp

野毛屋釣船店

Page Load Speed

7.4 sec in total

First Response

2.1 sec

Resources Loaded

5.1 sec

Page Rendered

129 ms

nogeya.jp screenshot

About Website

Click here to check amazing Nogeya content for Japan. Otherwise, check out these important facts you probably never knew about nogeya.jp

金沢八景の海釣りは野毛屋釣船店へ

Visit nogeya.jp

Key Findings

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

Performance Metrics

nogeya.jp performance score

0

Network Requests Diagram

nogeya.jp

2111 ms

showFirstPage.do

192 ms

top.html

185 ms

menu.html

339 ms

performTask.do

375 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that all of those requests were addressed to Nogeya.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Nogeya.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 kB (2%)

Content Size

111.5 kB

After Optimization

109.8 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Nogeya.jp main page is 111.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 110.5 kB which makes up the majority of the site volume.

HTML Optimization

-44%

Potential reduce by 392 B

  • Original 882 B
  • After minification 851 B
  • After compression 490 B

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 392 B or 44% of the original size.

Image Optimization

-1%

Potential reduce by 1.2 kB

  • Original 110.5 kB
  • After minification 109.3 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. Nogeya images are well optimized though.

CSS Optimization

-57%

Potential reduce by 96 B

  • Original 167 B
  • After minification 101 B
  • After compression 71 B

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. Nogeya.jp needs all CSS files to be minified and compressed as it can save up to 96 B or 57% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (50%)

Requests Now

32

After Optimization

16

  • AJAX
  • Images
  • CSS

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

Network Requests Diagram

nogeya.jp

nogeya.jp

2111 ms

showFirstPage.do

showFirstPage.do

192 ms

top.html

top.html

185 ms

menu.html

menu.html

339 ms

performTask.do

performTask.do

375 ms

top_back.gif

top_back.gif

192 ms

top_ngy_logo.gif

top_ngy_logo.gif

307 ms

top_backhome.gif

top_backhome.gif

328 ms

1pix_dot.gif

1pix_dot.gif

327 ms

top_anim.gif

top_anim.gif

538 ms

top_line.gif

top_line.gif

361 ms

nogeya_line_qr.png

nogeya_line_qr.png

2517 ms

menu_back.gif

menu_back.gif

217 ms

menu_tit_backa.gif

menu_tit_backa.gif

323 ms

arrow_rght.gif

arrow_rght.gif

344 ms

menu_tit_backb.gif

menu_tit_backb.gif

343 ms

menu_tit_backc.gif

menu_tit_backc.gif

393 ms

menu_botline.gif

menu_botline.gif

398 ms

smy-135_45.gif

smy-135_45.gif

485 ms

style.css

style.css

471 ms

sea.jpg

sea.jpg

632 ms

nogeya_tit.gif

nogeya_tit.gif

533 ms

8.gif

8.gif

534 ms

0.gif

0.gif

541 ms

5.gif

5.gif

609 ms

1.gif

1.gif

630 ms

2.gif

2.gif

711 ms

7.gif

7.gif

712 ms

syaka_tit.gif

syaka_tit.gif

721 ms

madai.jpg

madai.jpg

1097 ms

aoriika.jpg

aoriika.jpg

1116 ms

shousaifugu.png

shousaifugu.png

792 ms

nogeya_info.gif

nogeya_info.gif

890 ms

map.gif

map.gif

890 ms

Accessibility Review

nogeya.jp accessibility score

33

Accessibility Issues

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

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

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

nogeya.jp SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nogeya.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Nogeya.jp main page’s claimed encoding is shift_jis. 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

nogeya.jp

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