13.1 sec in total
714 ms
12.3 sec
75 ms
Visit jamo.jp now to see the best up-to-date Jamo content for Japan and also check out these interesting facts you probably never knew about jamo.jp
2000年設立。インテリアデザイナーとスタイリスト、リンクしながら積極的にコラボレーションを展開。「心が動く空間」を目指し、数々の空間を生み出してきました。雑誌のスタイリングページから、家具の制作、ウィンドーディスプレイ、リテイルストア、レストラン、オフィス、ホテルの設計までプロジェクトは多岐に渡ります。現在は設計に特化した活動を展開。生活の中で見過ごされたり、無意識のうちに忘れさられてしうような...
Visit jamo.jpWe analyzed Jamo.jp page load time and found that the first response time was 714 ms and then it took 12.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
jamo.jp performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value89.8 s
0/100
25%
Value24.0 s
0/100
10%
Value240 ms
86/100
30%
Value0
100/100
15%
Value4.6 s
82/100
10%
714 ms
334 ms
678 ms
2559 ms
544 ms
Our browser made a total of 29 requests to load all elements on the main page. We found that 93% of them (27 requests) were addressed to the original Jamo.jp, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (9.2 sec) belongs to the original domain Jamo.jp.
Page size can be reduced by 89.5 kB (1%)
6.2 MB
6.1 MB
In fact, the total size of Jamo.jp main page is 6.2 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. 15% of websites need less resources to load. Images take 6.1 MB which makes up the majority of the site volume.
Potential reduce by 5.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. This page needs HTML code to be minified as it can gain 1.1 kB, which is 15% 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 5.1 kB or 72% of the original size.
Potential reduce by 16.5 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. Jamo images are well optimized though.
Potential reduce by 64.6 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 64.6 kB or 57% of the original size.
Potential reduce by 3.4 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. Jamo.jp needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 76% of the original size.
Number of requests can be reduced by 3 (11%)
28
25
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jamo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
jamo.jp
714 ms
index.css
334 ms
modernizr.custom.69029.js
678 ms
jquery.js
2559 ms
jquery_easing.js
544 ms
ga.js
43 ms
logo.gif
168 ms
top17.jpg
2416 ms
top16.jpg
2038 ms
top15.jpg
1921 ms
top14.jpg
2319 ms
top13.jpg
3589 ms
top12.jpg
3462 ms
top11.jpg
5842 ms
top10.jpg
4709 ms
top09.jpg
5014 ms
top08.jpg
5343 ms
top07.jpg
5399 ms
top06.jpg
5134 ms
top05.jpg
7403 ms
top04.jpg
7891 ms
top03.jpg
7624 ms
top02.jpg
9166 ms
top01.jpg
8135 ms
catch.gif
6742 ms
space.gif
7118 ms
interior.gif
7613 ms
copyright.gif
7747 ms
__utm.gif
12 ms
jamo.jp 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
Image elements do not have [alt] attributes
jamo.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
jamo.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jamo.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 Jamo.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.
jamo.jp
Open Graph description is not detected on the main page of Jamo. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: