Tools & Wizards About Us
e-ippei.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

e-ippei.com

やきとりの一平本店

Page Load Speed

8.1 sec in total

First Response

589 ms

Resources Loaded

6.4 sec

Page Rendered

1.1 sec

e-ippei.com screenshot

About Website

Click here to check amazing E Ippei content. Otherwise, check out these important facts you probably never knew about e-ippei.com

室蘭のソウルフード室蘭やきとりをご提供いたします。 「豚肉、玉ねぎ、洋がらし」の伝統的な室蘭やきとりをご堪能いただけます。 創業昭和25年以来、古くから親しまれてきた、伝統の味を守りつつ、室蘭やきとりの発展と普及に力をいれております。

Visit e-ippei.com

Key Findings

We analyzed E-ippei.com page load time and found that the first response time was 589 ms and then it took 7.5 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

e-ippei.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value18.3 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value14.5 s

8/100

10%

Network Requests Diagram

e-ippei.com

589 ms

www.e-ippei.com

1960 ms

wp-emoji-release.min.js

193 ms

bootstrap.min.css

384 ms

style.min.css

527 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 64% of them (63 requests) were addressed to the original E-ippei.com, 28% (27 requests) were made to Static.xx.fbcdn.net and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain E-ippei.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 483.8 kB (4%)

Content Size

13.1 MB

After Optimization

12.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-ippei.com main page is 13.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 12.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 91.6 kB

  • Original 107.4 kB
  • After minification 102.4 kB
  • After compression 15.8 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 91.6 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 385.5 kB

  • Original 12.8 MB
  • After minification 12.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. E Ippei images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.2 kB

  • Original 167.5 kB
  • After minification 167.5 kB
  • After compression 165.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

-7%

Potential reduce by 4.4 kB

  • Original 66.3 kB
  • After minification 66.3 kB
  • After compression 61.8 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. E-ippei.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 54 (58%)

Requests Now

93

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e-ippei.com

e-ippei.com

589 ms

www.e-ippei.com

www.e-ippei.com

1960 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

193 ms

bootstrap.min.css

bootstrap.min.css

384 ms

style.min.css

style.min.css

527 ms

wp-show-posts-min.css

wp-show-posts-min.css

567 ms

css

css

35 ms

style.css

style.css

765 ms

elementor-icons.min.css

elementor-icons.min.css

575 ms

animations.min.css

animations.min.css

601 ms

frontend.min.css

frontend.min.css

831 ms

font-awesome.min.css

font-awesome.min.css

696 ms

post-1926.css

post-1926.css

754 ms

post-211.css

post-211.css

768 ms

css

css

33 ms

jquery.min.js

jquery.min.js

1010 ms

jquery-migrate.min.js

jquery-migrate.min.js

876 ms

preloader-script.js

preloader-script.js

943 ms

elementor.js

elementor.js

950 ms

functions.js

functions.js

951 ms

scripts.js

scripts.js

1163 ms

wp-embed.min.js

wp-embed.min.js

1164 ms

jquery.matchHeight.js

jquery.matchHeight.js

1175 ms

frontend-modules.min.js

frontend-modules.min.js

1177 ms

core.min.js

core.min.js

1176 ms

dialog.min.js

dialog.min.js

1202 ms

waypoints.min.js

waypoints.min.js

1254 ms

swiper.min.js

swiper.min.js

1386 ms

share-link.min.js

share-link.min.js

1361 ms

frontend.min.js

frontend.min.js

1634 ms

logo.png

logo.png

1847 ms

favicon.png

favicon.png

1396 ms

Kato-4723.jpg

Kato-4723.jpg

2688 ms

s2.jpg

s2.jpg

2908 ms

s3.jpg

s3.jpg

2076 ms

s5.jpg

s5.jpg

2191 ms

s6.jpg

s6.jpg

2491 ms

s7.jpg

s7.jpg

2310 ms

s8.jpg

s8.jpg

2259 ms

s9.jpg

s9.jpg

2599 ms

s10.jpg

s10.jpg

2256 ms

s11.jpg

s11.jpg

2135 ms

s4.jpg

s4.jpg

2101 ms

A1onten_yakitori-5694.jpg

A1onten_yakitori-5694.jpg

2130 ms

ls1.jpg

ls1.jpg

2139 ms

ls2.jpg

ls2.jpg

2217 ms

ls3.jpg

ls3.jpg

2113 ms

ls4.jpg

ls4.jpg

2164 ms

ls5.jpg

ls5.jpg

2148 ms

ls6.jpg

ls6.jpg

2148 ms

ls7.jpg

ls7.jpg

2153 ms

ls8.jpg

ls8.jpg

2156 ms

ls9.jpg

ls9.jpg

2891 ms

ls10.jpg

ls10.jpg

2132 ms

ls11.jpg

ls11.jpg

2156 ms

embed

embed

347 ms

page.php

page.php

368 ms

footerlogo3.png

footerlogo3.png

1956 ms

menubg3-1.jpg

menubg3-1.jpg

2013 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOtbHKrc.ttf

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOtbHKrc.ttf

43 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2071 ms

eicons.woff

eicons.woff

2096 ms

Ippei_alcool_bar-7379.jpg

Ippei_alcool_bar-7379.jpg

2295 ms

IMG_4775.jpg

IMG_4775.jpg

2127 ms

190130%E7%84%BC%E5%8F%B02-1.jpg

190130%E7%84%BC%E5%8F%B02-1.jpg

2156 ms

footer.jpg

footer.jpg

2201 ms

ichimibyodo_animated.svg

ichimibyodo_animated.svg

2101 ms

js

js

239 ms

Ql-UNnxapLj.css

Ql-UNnxapLj.css

28 ms

G8HUhdl8OvE.css

G8HUhdl8OvE.css

32 ms

65zeFj4kaoH.css

65zeFj4kaoH.css

37 ms

DaPJf3IFK7Z.js

DaPJf3IFK7Z.js

46 ms

8O2J-mJIMh1.js

8O2J-mJIMh1.js

30 ms

QCHZeiE_shc.js

QCHZeiE_shc.js

31 ms

4aFcRp6-srT.js

4aFcRp6-srT.js

36 ms

Mgao39tvtRW.js

Mgao39tvtRW.js

41 ms

Y4zFOWmUObv.js

Y4zFOWmUObv.js

43 ms

kY8eYg-9-SS.js

kY8eYg-9-SS.js

43 ms

DJbp39Fn87q.js

DJbp39Fn87q.js

93 ms

p55HfXW__mM.js

p55HfXW__mM.js

92 ms

25lpsvLC9vq.js

25lpsvLC9vq.js

96 ms

0oAcl5WIW_m.js

0oAcl5WIW_m.js

94 ms

0bio7TMsDws.js

0bio7TMsDws.js

96 ms

ODJ37xNnscq.js

ODJ37xNnscq.js

102 ms

re7HGUsWRjJ.js

re7HGUsWRjJ.js

109 ms

m9GkTPGJdFk.js

m9GkTPGJdFk.js

100 ms

2J3sA3WyJKG.js

2J3sA3WyJKG.js

100 ms

3o3KXahxag9.js

3o3KXahxag9.js

125 ms

QoMTH0SpLC5.js

QoMTH0SpLC5.js

127 ms

kgAz0TBWoYE.js

kgAz0TBWoYE.js

136 ms

pYF1ZB4Vs2U.js

pYF1ZB4Vs2U.js

134 ms

HzxD9aAXSyD.js

HzxD9aAXSyD.js

135 ms

383815370_811834540944844_3810636332800174015_n.jpg

383815370_811834540944844_3810636332800174015_n.jpg

265 ms

366741289_783224960472469_2138766757380357398_n.jpg

366741289_783224960472469_2138766757380357398_n.jpg

130 ms

2e_sPiaNxu9.js

2e_sPiaNxu9.js

101 ms

NuRKTpHUY_A.js

NuRKTpHUY_A.js

99 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

98 ms

frontend-msie.min.css

frontend-msie.min.css

1816 ms

Accessibility Review

e-ippei.com accessibility score

92

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

e-ippei.com 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

e-ippei.com SEO score

73

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    JA

  • Encoding

    UTF-8

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

e-ippei.com

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