8.7 sec in total
1.4 sec
6.9 sec
389 ms
Click here to check amazing Pepper Lunch content for Japan. Otherwise, check out these important facts you probably never knew about pepperlunch.com
ペッパーランチの公式ウェブサイト 新メニューやキャンペーンなどペッパーランチのお得な最新情報と、営業時間やデリバリー対応店舗といった便利な情報が盛り沢山!
Visit pepperlunch.comWe analyzed Pepperlunch.com page load time and found that the first response time was 1.4 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
pepperlunch.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value7.0 s
6/100
25%
Value5.9 s
48/100
10%
Value370 ms
71/100
30%
Value0.017
100/100
15%
Value5.6 s
69/100
10%
1380 ms
575 ms
581 ms
583 ms
607 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 59% of them (72 requests) were addressed to the original Pepperlunch.com, 20% (24 requests) were made to Static.xx.fbcdn.net and 12% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Pepperlunch.com.
Page size can be reduced by 400.2 kB (13%)
3.0 MB
2.6 MB
In fact, the total size of Pepperlunch.com main page is 3.0 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 13.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 13.3 kB or 70% of the original size.
Potential reduce by 153.4 kB
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. Pepper Lunch images are well optimized though.
Potential reduce by 220.2 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 220.2 kB or 73% of the original size.
Potential reduce by 13.3 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. Pepperlunch.com needs all CSS files to be minified and compressed as it can save up to 13.3 kB or 79% of the original size.
Number of requests can be reduced by 35 (29%)
120
85
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pepper Lunch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
pepperlunch.com
1380 ms
base.css
575 ms
common.css
581 ms
top.css
583 ms
smoothscroll.js
607 ms
jquery-1.7.1.js
2007 ms
heightLine.js
573 ms
alphafilter.js
764 ms
sp.js
765 ms
conversion.js
18 ms
r-pr001.jpg
1359 ms
bg.gif
390 ms
logo.png
602 ms
menu00.png
192 ms
menu01.png
194 ms
menu03.png
203 ms
menu04.png
194 ms
menu05.png
386 ms
nav_left.png
389 ms
nav_home_on.png
388 ms
nav_blank.png
401 ms
nav_campign.png
582 ms
nav_menu.png
582 ms
nav_restaurant.png
581 ms
nav_about.png
583 ms
nav_ranking.png
600 ms
nav_secure.png
766 ms
nav_right.png
770 ms
line_home.png
1348 ms
main-visual51.jpg
2721 ms
main-visual52.jpg
2595 ms
main-visual03.jpg
2200 ms
main-visual08.jpg
2323 ms
main-visual05.jpg
2726 ms
aboutus_title.gif
1540 ms
aboutus_lead.gif
1732 ms
btn_detail.gif
1925 ms
ranking_title.png
2309 ms
ranking_btn.gif
2400 ms
01.png
2501 ms
02.png
2512 ms
03.png
2601 ms
news_title.gif
2692 ms
btn_news.gif
2701 ms
pepperlice_banner.jpg
3193 ms
bnr_menu.png
3000 ms
r-st005.jpg
1361 ms
burg150.jpg
2017 ms
widgets.js
7 ms
bnr_eatting.png
3064 ms
67 ms
ga.js
53 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
21 ms
like.php
135 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
31 ms
likebox.php
250 ms
68 ms
__utm.gif
31 ms
34 ms
bnr_shop.png
3461 ms
bnr_world.png
2723 ms
newshop_bg.png
2727 ms
movie_bg.png
3096 ms
vpc6VNjRPXV.js
304 ms
LVx-xkvaJ0b.png
225 ms
jot
114 ms
jTuqQ-OPDr6.css
168 ms
n370yiaI2G6.css
172 ms
uzCGVqplqq-.css
176 ms
_rx8naC75Dy.js
213 ms
x5F9OMjKyLw.js
268 ms
ICDbTSzjQEg.js
204 ms
TTCre3391I0.js
209 ms
rFmE1g6Dkoz.js
317 ms
7cm7D75Y0Sf.js
287 ms
C-h3nYPqETO.js
291 ms
oRoBXlHCpEy.js
249 ms
336JejShbZp.js
265 ms
sj-JwAJi4AH.js
289 ms
DKRU1bYTkTw.js
304 ms
ZNPAadQNc33.js
301 ms
W0OV23mIOyO.js
361 ms
36TdwhIHusi.js
363 ms
bnr_app.gif
2726 ms
blog_banner.jpg
2817 ms
btn_fc.gif
2886 ms
btn_recruit.gif
2916 ms
btn_pagetop.gif
2998 ms
icon.gif
2825 ms
main-visual_bg.png
2883 ms
thum04.png
2908 ms
thum08.png
2914 ms
thum01.png
2998 ms
thum02.png
3006 ms
12360070_674559792646719_4183970703768607170_n.jpg
246 ms
1898226_432257816876919_823673362_n.jpg
283 ms
313374_109801622465024_97728701_n.jpg
320 ms
12246617_908135205936746_6237259509501716356_n.jpg
377 ms
1379841_10150004552801901_469209496895221757_n.jpg
357 ms
12240131_1530263290629814_7305345041588174121_n.jpg
358 ms
644261_188226708026547_1108419620_n.jpg
362 ms
12227565_763765450419111_8683004727316346079_n.jpg
363 ms
12717417_1098682823498899_5250065361156197137_n.jpg
365 ms
12647341_977134902334554_7568965530666186671_n.jpg
394 ms
148636_593859154022049_167997846_n.jpg
394 ms
12745632_765269073607985_382171517896541921_n.jpg
401 ms
10401395_155268858191002_2007479039531048425_n.jpg
402 ms
603932_114900488669016_1532239641_n.jpg
401 ms
205491_442797175779377_1575430438_n.jpg
414 ms
wL6VQj7Ab77.png
80 ms
s7jcwEQH7Sx.png
79 ms
pUFVdPjIRct.png
47 ms
thum03.png
2891 ms
aboutus_bg.png
2913 ms
I6-MnjEovm5.js
44 ms
vlXaquuXMrr.js
40 ms
ranking_bg.png
2342 ms
ranking_itembg.png
2258 ms
box610_top.png
2090 ms
box610_bottom.png
1916 ms
box610_body.png
1649 ms
icon_blank.gif
1565 ms
thum04_on.png
1559 ms
pepperlunch.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pepperlunch.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
pepperlunch.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pepperlunch.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 Pepperlunch.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.
pepperlunch.com
Open Graph data is detected on the main page of Pepper Lunch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: