Tools & Wizards About Us
1930.jp screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

1930.jp

伊豆の味[徳造丸]公式ショッピングサイト 伊豆ひもの,金目鯛,伊勢海老, トコロテン,伊豆グルメ ギフト,伊豆名物おみやげ,名産特産お土産(とくぞうまる1930.jp)

Page Load Speed

9 sec in total

First Response

950 ms

Resources Loaded

7.1 sec

Page Rendered

943 ms

1930.jp screenshot

About Website

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

[伊豆の味　徳造丸]は、伊豆稲取にて大正末期に金目鯛やサバ漁を営む“網元”として創業致しました。現在では金目鯛料理・伊勢海老料理などの海鮮料理・寿司・丼・郷土料理などの食事処、金目鯛煮魚・魚屋厳選伊豆グルメのいか塩辛・伊豆稲取ところてん心太・ボイル伊勢海老,ひもの干物などの海産物をはじめ、伊豆箱根富士の地場産品を販売する海鮮家（直営販売店）・インターネットショッピングやカタログ通販の事業を行い、箱...

Visit 1930.jp

Key Findings

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

Performance Metrics

1930.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value21.3 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.722

6/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

1930.jp

950 ms

main.css

404 ms

left_navi.js

374 ms

imagelink.js

366 ms

newslink.js

389 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 90% of them (82 requests) were addressed to the original 1930.jp, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain 1930.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 892.0 kB (12%)

Content Size

7.4 MB

After Optimization

6.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1930.jp main page is 7.4 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 6.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 26.6 kB

  • Original 32.8 kB
  • After minification 21.3 kB
  • After compression 6.2 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 11.5 kB, which is 35% 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 26.6 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 400.2 kB

  • Original 6.8 MB
  • After minification 6.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. 1930 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 247.0 kB

  • Original 359.8 kB
  • After minification 335.9 kB
  • After compression 112.8 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 247.0 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 218.2 kB

  • Original 263.1 kB
  • After minification 257.5 kB
  • After compression 44.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. 1930.jp needs all CSS files to be minified and compressed as it can save up to 218.2 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

88

After Optimization

74

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1930. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

1930.jp

1930.jp

950 ms

main.css

main.css

404 ms

left_navi.js

left_navi.js

374 ms

imagelink.js

imagelink.js

366 ms

newslink.js

newslink.js

389 ms

menu_navi.js

menu_navi.js

349 ms

jquery.bxslider.js

jquery.bxslider.js

716 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

562 ms

jquery.bxslider.css

jquery.bxslider.css

637 ms

jquery.min.js

jquery.min.js

7 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

812 ms

jquery.bxslider.css

jquery.bxslider.css

807 ms

analytics.js

analytics.js

25 ms

bg_body2.gif

bg_body2.gif

812 ms

logo.gif

logo.gif

347 ms

logo2.gif

logo2.gif

672 ms

gnavi0.png

gnavi0.png

342 ms

gnavi1.png

gnavi1.png

540 ms

gnavi2.png

gnavi2.png

545 ms

gnavi3.png

gnavi3.png

550 ms

gnavi4.png

gnavi4.png

875 ms

img01.jpg

img01.jpg

1567 ms

img02.jpg

img02.jpg

1819 ms

img03.jpg

img03.jpg

1045 ms

img04.jpg

img04.jpg

1442 ms

img05.jpg

img05.jpg

1938 ms

img06.jpg

img06.jpg

2087 ms

img07.jpg

img07.jpg

1716 ms

img08.jpg

img08.jpg

2187 ms

img09.jpg

img09.jpg

2745 ms

img10.jpg

img10.jpg

2048 ms

img11.jpg

img11.jpg

2352 ms

photo01.jpg

photo01.jpg

2167 ms

photo02.jpg

photo02.jpg

2322 ms

photo03.jpg

photo03.jpg

2299 ms

photo04.jpg

photo04.jpg

2405 ms

photo05.jpg

photo05.jpg

2374 ms

photo06.jpg

photo06.jpg

2525 ms

photo07.jpg

photo07.jpg

2542 ms

photo08.jpg

photo08.jpg

2828 ms

photo10.jpg

photo10.jpg

2551 ms

photo11.jpg

photo11.jpg

2666 ms

tvasahi20160226.jpg

tvasahi20160226.jpg

2898 ms

tvasahi20160226_2.jpg

tvasahi20160226_2.jpg

2929 ms

tvasahi20160226_3.jpg

tvasahi20160226_3.jpg

2878 ms

thefishing01.jpg

thefishing01.jpg

2925 ms

thefishing02.jpg

thefishing02.jpg

3011 ms

twitter20160121.jpg

twitter20160121.jpg

3205 ms

olivefarm20151129_1.jpg

olivefarm20151129_1.jpg

3208 ms

widgets.js

widgets.js

191 ms

ijswfH6nGW4

ijswfH6nGW4

111 ms

collect

collect

31 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

20 ms

www-embed-player.js

www-embed-player.js

44 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

36 ms

ad_status.js

ad_status.js

41 ms

banner14.jpg

banner14.jpg

3542 ms

banner_catalog.jpg

banner_catalog.jpg

2839 ms

banner_webcatalog.jpg

banner_webcatalog.jpg

2584 ms

banner16.jpg

banner16.jpg

3203 ms

banner20.jpg

banner20.jpg

4314 ms

amimoto02.jpg

amimoto02.jpg

2712 ms

amimoto03.jpg

amimoto03.jpg

2592 ms

banner21.jpg

banner21.jpg

4175 ms

amimoto01.jpg

amimoto01.jpg

2533 ms

banner23.jpg

banner23.jpg

2666 ms

kaisenya01.jpg

kaisenya01.jpg

2224 ms

kaisenya02.jpg

kaisenya02.jpg

2219 ms

kaisenya03.jpg

kaisenya03.jpg

2216 ms

kaisenya04.jpg

kaisenya04.jpg

2121 ms

kaisenya05.jpg

kaisenya05.jpg

2062 ms

kaisenya06.jpg

kaisenya06.jpg

2149 ms

kaisenya07.jpg

kaisenya07.jpg

2055 ms

kaisenya08.jpg

kaisenya08.jpg

2134 ms

kaisenya09.jpg

kaisenya09.jpg

2005 ms

kyodo.jpg

kyodo.jpg

2443 ms

topimage01.jpg

topimage01.jpg

2874 ms

menu01.jpg

menu01.jpg

2109 ms

menu02.jpg

menu02.jpg

2090 ms

menu03.jpg

menu03.jpg

2137 ms

menu04.jpg

menu04.jpg

2144 ms

menu05.jpg

menu05.jpg

2282 ms

bg_h2.gif

bg_h2.gif

2215 ms

bg_info_line.gif

bg_info_line.gif

2186 ms

honten.jpg

honten.jpg

2671 ms

bg_pagetop.gif

bg_pagetop.gif

2141 ms

bx_loader.gif

bx_loader.gif

2207 ms

bg_gnavi1.png

bg_gnavi1.png

2196 ms

prev1.png

prev1.png

2260 ms

next1.png

next1.png

2218 ms

bg_gnavi2.png

bg_gnavi2.png

2182 ms

Accessibility Review

1930.jp accessibility score

69

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

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

High

Browser errors were logged to the console

SEO Factors

1930.jp SEO score

69

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

    JA

  • Encoding

    UTF-8

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

1930.jp

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