Access owner.co.jp. 株式会社オーナーばり｜海釣り仕掛け、投げ釣り仕掛け、釣り針、淡水仕掛けなど、釣具全般商品を製造・販売

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value1,850 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

owner.co.jp

859 ms

common.css

799 ms

scr.js

331 ms

top.css

505 ms

news.css

352 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 95% of them (123 requests) were addressed to the original Owner.co.jp, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Owner.co.jp.

Content Size

3.2 MB

After Optimization

2.7 MB

In fact, the total size of Owner.co.jp main page is 3.2 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 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 221.4 kB

Original 241.9 kB
After minification 191.4 kB
After compression 20.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 50.6 kB, which is 21% 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 221.4 kB or 91% of the original size.

Image Optimization

-1%

Potential reduce by 20.2 kB

Original 2.6 MB
After minification 2.6 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. Owner images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 158.7 kB

Original 227.8 kB
After minification 203.5 kB
After compression 69.1 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 158.7 kB or 70% of the original size.

CSS Optimization

-90%

Potential reduce by 63.8 kB

Original 71.2 kB
After minification 53.7 kB
After compression 7.4 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. Owner.co.jp needs all CSS files to be minified and compressed as it can save up to 63.8 kB or 90% of the original size.

Requests Now

127

After Optimization

109

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

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

owner.co.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

株式会社オーナーばり｜海釣り仕掛け、投げ釣り仕掛け、釣り針、淡水仕掛けなど、釣具全般商品を製造・販売

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

owner.co.jp

common.css

scr.js

top.css

news.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

owner.co.jp

common.css

scr.js

top.css

news.css

camera.css

jquery.min.js

jquery.easing.1.3.js

camera.min.js

camera.js

bg01.jpg

head.jpg

dummy.gif

menu.jpg

artinus_top.jpg

yumetyoko.jpg

tl_bn27.jpg

tl_bn02.jpg

tl_bn03.jpg

stingerbanner.jpg

tl_bn04.jpg

tl_bn07.jpg

tl_bn08.jpg

link_top.jpg

blog.jpg

mobile_top.jpg

recruit_bn_top2.jpg

anglers-chance.jpg

anglersadol2016.jpg

ownermovie.jpg

draw4sp.jpg

gekito_banner.jpg

new_tit.jpg

foot_line.jpg

link_usa.gif

link_taiwan.gif

link_china.gif

link.gif

all.js

b_bn01.jpg

b_bn02.jpg

b_bn05.jpg

ow_bn26.jpg