6.9 sec in total
527 ms
6 sec
380 ms
Visit notrunks.jp now to see the best up-to-date No TRUNKS content and also check out these interesting facts you probably never knew about notrunks.jp
中央線国立駅徒歩5分、その昔名器と謳われたアルテックA7(小劇場用スピーカー)が鎮座するジャズ中心のダイニングバーです。酒も飲めて、料理もそこそこ、週末にはライブも楽しめる。そんなジャズの発信基地が目標です。ジャズ・バーとしての比重が高いと思いますが是非遊びに来てください。ジャズの奥深さを共に楽しみましょう。
Visit notrunks.jpWe analyzed Notrunks.jp page load time and found that the first response time was 527 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
notrunks.jp performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value6.4 s
10/100
25%
Value17.5 s
0/100
10%
Value460 ms
62/100
30%
Value0.015
100/100
15%
Value20.5 s
2/100
10%
527 ms
1665 ms
485 ms
77 ms
106 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 79% of them (37 requests) were addressed to the original Notrunks.jp, 6% (3 requests) were made to Use.fontawesome.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Notrunks.jp.
Page size can be reduced by 739.3 kB (12%)
5.9 MB
5.2 MB
In fact, the total size of Notrunks.jp main page is 5.9 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. 40% of websites need less resources to load. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 52.2 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 11.3 kB, which is 16% 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 52.2 kB or 76% of the original size.
Potential reduce by 223.7 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. No TRUNKS images are well optimized though.
Potential reduce by 411.0 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 411.0 kB or 66% of the original size.
Potential reduce by 52.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. Notrunks.jp needs all CSS files to be minified and compressed as it can save up to 52.5 kB or 76% of the original size.
Number of requests can be reduced by 12 (29%)
41
29
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of No TRUNKS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
notrunks.jp
527 ms
notrunks.jp
1665 ms
styles.css
485 ms
js
77 ms
js
106 ms
all.css
44 ms
jquery.min.js
38 ms
styles.css
487 ms
n2-ss-2.css
649 ms
jquery.js
1114 ms
jquery-migrate.min.js
563 ms
scripts.js
427 ms
wp-embed.min.js
324 ms
css
29 ms
css
45 ms
wp-emoji-release.min.js
163 ms
78500b9016d93f187b0491448bbba900.js
1292 ms
logo01.png
188 ms
logo02.png
324 ms
icon-insta-w.png
189 ms
icon-twitter-w.png
188 ms
icon-facebook-w.png
188 ms
slider_floor01-05.jpg
1616 ms
slider_live04.jpg
1340 ms
slide_03_220426_shochu.jpg
1675 ms
slider_floor02-04.jpg
2047 ms
click.png
486 ms
top-about02-06.jpg
1614 ms
bn-fooddrink-292.jpg
1443 ms
drinkimage_02.jpg
1674 ms
foodimage_03.jpg
1767 ms
bn-sound03-292.jpg
1777 ms
bn-liveevent04-292.jpg
1778 ms
202406131a-thumbnail2.jpg
1861 ms
PXL_20240216_120857867.jpg
1861 ms
collage.png
2414 ms
collage-1.png
2583 ms
PXL_20240315_112458250.jpg
2101 ms
collage-2.png
2977 ms
RIMG0090.jpg
2048 ms
icon-insta.jpg
2232 ms
icon-twitter.jpg
2234 ms
icon-facebook.jpg
2262 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
30 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
29 ms
fa-solid-900.woff
12 ms
fa-regular-400.woff
34 ms
notrunks.jp accessibility score
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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.
notrunks.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
notrunks.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Notrunks.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 Notrunks.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.
notrunks.jp
Open Graph data is detected on the main page of No TRUNKS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: