Tools & Wizards About Us
uocho.co.jp screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

uocho.co.jp

函館一の生鮮鮮魚の品揃え！　スーパー魚長

Page Load Speed

8.5 sec in total

First Response

616 ms

Resources Loaded

7.3 sec

Page Rendered

601 ms

uocho.co.jp screenshot

About Website

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

北海道函館・スーパー魚長のホームページです。毎日の魚長チラシや特売情報を閲覧することができます。オンラインショッピングも行っています。

Visit uocho.co.jp

Key Findings

We analyzed Uocho.co.jp page load time and found that the first response time was 616 ms and then it took 7.9 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

uocho.co.jp performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

uocho.co.jp

616 ms

www.uocho.co.jp

1614 ms

gtm.js

58 ms

style.css

211 ms

middle.css

420 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 93.1 kB (3%)

Content Size

3.6 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 12.1 kB

  • Original 16.4 kB
  • After minification 15.8 kB
  • After compression 4.3 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 12.1 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 77.4 kB

  • Original 3.5 MB
  • After minification 3.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. Uocho images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.6 kB

  • Original 68.9 kB
  • After minification 68.9 kB
  • After compression 67.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 2.1 kB

  • Original 33.1 kB
  • After minification 33.1 kB
  • After compression 31.0 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. Uocho.co.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (47%)

Requests Now

57

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

uocho.co.jp

uocho.co.jp

616 ms

www.uocho.co.jp

www.uocho.co.jp

1614 ms

gtm.js

gtm.js

58 ms

style.css

style.css

211 ms

middle.css

middle.css

420 ms

jquery.mmenu.all.css

jquery.mmenu.all.css

621 ms

slider-pro.css

slider-pro.css

624 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

844 ms

jquery.mmenu.all.js

jquery.mmenu.all.js

840 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

632 ms

jquery.sliderPro.min.js

jquery.sliderPro.min.js

942 ms

common.js

common.js

826 ms

ga.js

ga.js

1593 ms

fortheelderly.css

fortheelderly.css

422 ms

childrens_marathon.css

childrens_marathon.css

614 ms

recommended.css

recommended.css

629 ms

shoprecommended.css

shoprecommended.css

631 ms

news.css

news.css

634 ms

shop.css

shop.css

758 ms

flyer.css

flyer.css

820 ms

service.css

service.css

838 ms

company.css

company.css

839 ms

privacy.css

privacy.css

844 ms

inquiry.css

inquiry.css

992 ms

recruit.css

recruit.css

1026 ms

r_requirements.css

r_requirements.css

1048 ms

r_entry.css

r_entry.css

1048 ms

r_interview.css

r_interview.css

1053 ms

r_message.css

r_message.css

1227 ms

r_scholarship.css

r_scholarship.css

1232 ms

r_s_entry.css

r_s_entry.css

1257 ms

line.css

line.css

1258 ms

logo.png

logo.png

210 ms

logo2.png

logo2.png

236 ms

inquiry_link.png

inquiry_link.png

209 ms

head_recruit_2019.png

head_recruit_2019.png

211 ms

head_home.png

head_home.png

208 ms

top01_2023.jpg

top01_2023.jpg

1669 ms

top02_2023.png

top02_2023.png

1033 ms

top06_gift_202406.jpg

top06_gift_202406.jpg

2275 ms

top04_202008.jpg

top04_202008.jpg

1463 ms

news_calendar2-300x209.png

news_calendar2-300x209.png

632 ms

76d9c099756c6baec84cb7645da40cfe-212x300.jpg

76d9c099756c6baec84cb7645da40cfe-212x300.jpg

472 ms

2024_marathon-213x300.png

2024_marathon-213x300.png

1177 ms

5ba897d6d697425ab4b38f14e988b482-300x207.png

5ba897d6d697425ab4b38f14e988b482-300x207.png

1053 ms

top_flyer.png

top_flyer.png

1858 ms

top_shoprecommended.png

top_shoprecommended.png

1473 ms

syacho_anim.gif

syacho_anim.gif

3096 ms

b02_newcard.png

b02_newcard.png

1672 ms

b10.png

b10.png

1684 ms

b04.png

b04.png

1878 ms

b05.png

b05.png

1883 ms

b06.png

b06.png

1896 ms

b11.jpg

b11.jpg

3300 ms

link01.png

link01.png

2086 ms

b12_202008.jpg

b12_202008.jpg

2513 ms

link02.png

link02.png

2105 ms

b13_2019.jpg

b13_2019.jpg

3131 ms

link03.png

link03.png

2316 ms

footer_logo.png

footer_logo.png

2480 ms

openhand.cur

openhand.cur

3068 ms

Accessibility Review

uocho.co.jp accessibility score

55

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.

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

uocho.co.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

uocho.co.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

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

High

Tap targets are not sized appropriately

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 Uocho.co.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 Uocho.co.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

uocho.co.jp

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