Access unase.jp. うな瀬のホームページ

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

unase.jp

534 ms

www.unase.jp

611 ms

A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20211130+jqtransform.css,Mcc.RMfxFs7Pct.css.pagespeed.cf.dO3BCQIoPm.css

724 ms

jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js

895 ms

ajax_v2016.js.pagespeed.jm.DiYDmwJy8A.js

555 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 61% of them (41 requests) were addressed to the original Unase.jp, 25% (17 requests) were made to Web.xaas3.jp and 6% (4 requests) were made to S1873742.xaas3.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Unase.jp.

Content Size

2.1 MB

After Optimization

2.0 MB

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

HTML Optimization

-73%

Potential reduce by 38.6 kB

Original 52.7 kB
After minification 52.0 kB
After compression 14.1 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 38.6 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 25.8 kB

Original 1.9 MB
After minification 1.8 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. Unase images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 865 B

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

CSS Optimization

-6%

Potential reduce by 3.3 kB

Original 58.4 kB
After minification 58.4 kB
After compression 55.1 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. Unase.jp has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA input fields do not have accessible names

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

High

Links do not have a discernible name

High

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

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

unase.jp

Open Graph data is detected on the main page of Unase. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

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

unase.jp

www.unase.jp

A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20211130+jqtransform.css,Mcc.RMfxFs7Pct.css.pagespeed.cf.dO3BCQIoPm.css

jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js

ajax_v2016.js.pagespeed.jm.DiYDmwJy8A.js

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

unase.jp

www.unase.jp

A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20211130+jqtransform.css,Mcc.RMfxFs7Pct.css.pagespeed.cf.dO3BCQIoPm.css

jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js

ajax_v2016.js.pagespeed.jm.DiYDmwJy8A.js

jcarousellite_v1.1.js.pagespeed.jm.wtlzVdCKLg.js

mousewheel_v3.1.13.js.pagespeed.jm.wBwlG6vk-c.js

jscrollpane.js.pagespeed.jm.2wYEC_BNG3.js

treeview.js.pagespeed.jm.Ccxdh7coVu.js

common_v2016.js.pagespeed.jm.oX05TNZMmL.js

prettyphoto_v3.1.6.js,q20150527.pagespeed.jm.w2fGLjjfmp.js

theme.css

addStyle.css

main.css

bundle.js

api.js.pagespeed.jm.8b0_VoT09a.js

ex.js

main.js

searchGoodsView.js.pagespeed.jm.NQ81Ahg-XC.js

categoryView.js.pagespeed.jm.hZ_jgsTYCK.js

common.css

xspace.gif.pagespeed.ic.lRMfmktUso.png

rkFooter_dgyDb.gif

image1.jpg

sp_image1.jpg

image2.jpg

sp_image2.jpg

image3.jpg

sp_image3.jpg

bnr_img001.jpg

sp_bnr_img001.jpg

bnr_img002.jpg

sp_bnr_img002.jpg

bnr_img003.jpg

sp_bnr_img003.jpg

bnr_img004.jpg

sp_bnr_img004.jpg

bnr_img005.jpg

sp_bnr_img005.jpg

bnr_img006.jpg

sp_bnr_img006.jpg

bnr_img007.jpg

sp_bnr_img007.jpg