16.8 sec in total
1.6 sec
13.9 sec
1.3 sec
Click here to check amazing Kandalunch content. Otherwise, check out these important facts you probably never knew about kandalunch.net
神田駅周辺の安くておいしいお店をレポートします
Visit kandalunch.netWe analyzed Kandalunch.net page load time and found that the first response time was 1.6 sec and then it took 15.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kandalunch.net performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value12.3 s
0/100
25%
Value11.1 s
6/100
10%
Value620 ms
48/100
30%
Value0.991
2/100
15%
Value15.5 s
7/100
10%
1644 ms
356 ms
743 ms
529 ms
777 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 60% of them (78 requests) were addressed to the original Kandalunch.net, 11% (14 requests) were made to O.twimg.com and 5% (7 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (10.8 sec) belongs to the original domain Kandalunch.net.
Page size can be reduced by 436.6 kB (2%)
21.4 MB
20.9 MB
In fact, the total size of Kandalunch.net main page is 21.4 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. 85% 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 20.9 MB which makes up the majority of the site volume.
Potential reduce by 61.5 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 61.5 kB or 82% of the original size.
Potential reduce by 135.6 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. Kandalunch images are well optimized though.
Potential reduce by 125.9 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 125.9 kB or 49% of the original size.
Potential reduce by 113.5 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. Kandalunch.net needs all CSS files to be minified and compressed as it can save up to 113.5 kB or 81% of the original size.
Number of requests can be reduced by 43 (33%)
129
86
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kandalunch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
kandalunch.net
1644 ms
style.css
356 ms
font-awesome.min.css
743 ms
style.css
529 ms
extension.css
777 ms
responsive-pc.css
785 ms
style.css
531 ms
sns-viral-white.css
720 ms
wpp.css
534 ms
jquery.js
1670 ms
jquery-migrate.min.js
923 ms
loader.js
132 ms
vertical-s.css
730 ms
style.css
1346 ms
adsbygoogle.js
4 ms
nivo-slider.css
251 ms
public.css
266 ms
default.css
368 ms
javascript.js
848 ms
javascript.js
468 ms
wp-embed.min.js
554 ms
jquery.nivo.slider.pack.js
952 ms
ga.js
17 ms
wp-emoji-release.min.js
790 ms
__utm.gif
14 ms
background.jpg
1604 ms
IMG_8882-680x400.jpg
1180 ms
e577ae2f49252bf26ac9b579ac90224e-680x400.jpg
830 ms
IMG_2631-680x400.jpg
454 ms
IMG_2356-680x400.jpg
1283 ms
34067f74cf380a318be4e98d03cb1fd8-680x400.jpg
1272 ms
IMG_1783-680x400.jpg
1485 ms
IMG_1634-680x400.jpg
1465 ms
IMG_1191-680x400.jpg
2243 ms
IMG_1698-680x400.jpg
2324 ms
IMG_1218-680x400.jpg
2411 ms
IMG_1736-680x400.jpg
1897 ms
IMG_1532-680x400.jpg
2605 ms
IMG_4274-680x400.jpg
2739 ms
IMG_1657-680x400.jpg
3499 ms
IMG_2148-680x400.jpg
3743 ms
IMG_1805-680x400.jpg
3873 ms
IMG_1459-680x400.jpg
4001 ms
IMG_1241-680x400.jpg
4180 ms
IMG_1231-680x400.jpg
4013 ms
022623-680x400.jpg
4940 ms
ec847577050a52679be941ae245f8c00-680x400.jpg
4470 ms
e577ae2f49252bf26ac9b579ac90224e-150x150.jpg
4353 ms
34067f74cf380a318be4e98d03cb1fd8-150x150.jpg
4515 ms
ec847577050a52679be941ae245f8c00-150x150.jpg
4188 ms
12092440_1682765341946840_625891943_n.jpg
5998 ms
IMG_8929.jpg
9151 ms
IMG_8882.jpg
7595 ms
IMG_8834.jpg
8713 ms
IMG_8598.jpg
10827 ms
IMG_7984.jpg
10317 ms
IMG_7968.jpg
10354 ms
657-featured-75x75.jpg
7839 ms
502-featured-75x75.jpg
8082 ms
583-featured-75x75.jpg
8297 ms
ca-pub-0554116298964746.js
76 ms
zrt_lookup.html
173 ms
show_ads_impl.js
106 ms
widgets.js
111 ms
ads
290 ms
osd.js
78 ms
sdk.js
63 ms
ads
260 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
190 ms
ads
291 ms
fontawesome-webfont.woff
8307 ms
ads
291 ms
228 ms
xd_arbiter.php
58 ms
xd_arbiter.php
71 ms
m_js_controller.js
146 ms
abg.js
171 ms
syndication
274 ms
489897569980395520
372 ms
googlelogo_color_112x36dp.png
229 ms
16260142530956299493
202 ms
icomoon.woff
8249 ms
favicon
121 ms
nessie_icon_tiamat_white.png
91 ms
17287475847035435716
86 ms
s
78 ms
x_button_blue2.png
49 ms
1237024724226808665
66 ms
415-featured-75x75.jpg
8211 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
7 ms
proxy.jpg
233 ms
proxy.jpg
217 ms
proxy.jpg
261 ms
proxy.jpg
86 ms
proxy.jpg
214 ms
proxy.jpg
178 ms
proxy.jpg
352 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
37 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
70 ms
bf10f42d167ff6cdb17bac8a894863ad_normal.jpeg
232 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
43 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
48 ms
250-featured-75x75.jpg
8031 ms
proxy.jpg
212 ms
proxy.jpg
172 ms
proxy.jpg
122 ms
158-featured-75x75.jpg
8006 ms
567-featured-75x75.jpg
8057 ms
proxy.jpg
31 ms
proxy.jpg
151 ms
proxy.jpg
58 ms
proxy.jpg
130 ms
622-featured-75x75.jpg
7988 ms
37-featured-75x75.jpg
8038 ms
7-featured-75x75.jpg
7919 ms
686-featured-75x75.jpg
7799 ms
activeview
12 ms
651-featured-75x75.jpg
7449 ms
678-featured-75x75.jpg
7445 ms
jot.html
27 ms
529-featured-75x75.jpg
7456 ms
331-featured-75x75.jpg
7341 ms
258-featured-75x75.jpg
7273 ms
704-featured-75x75.jpg
6542 ms
170-featured-75x75.jpg
6457 ms
354-featured-75x75.jpg
6389 ms
577-featured-75x75.jpeg
6216 ms
arrows.png
6436 ms
bullets.png
6213 ms
print.css
179 ms
kandalunch.net accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
kandalunch.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
kandalunch.net 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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kandalunch.net 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 Kandalunch.net 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.
kandalunch.net
Open Graph data is detected on the main page of Kandalunch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: