10.2 sec in total
1.4 sec
8 sec
723 ms
Visit 4cm.jp now to see the best up-to-date 4 Cm content for Japan and also check out these interesting facts you probably never knew about 4cm.jp
美容室4cmは石川県金沢市を中心に広坂(しいのき迎賓館近く)、竪町(タテマチ)、諸江、横川、野々市に5店舗展開している美容室(美容院)です。七五三、成人式、卒業式、結婚式などのセット、メイク、着付けもお任せください。求人をご希望の方もお気軽にお問い合わせください。
Visit 4cm.jpWe analyzed 4cm.jp page load time and found that the first response time was 1.4 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
4cm.jp performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value12.8 s
0/100
25%
Value14.2 s
1/100
10%
Value640 ms
46/100
30%
Value0
100/100
15%
Value12.5 s
14/100
10%
1402 ms
1215 ms
712 ms
1482 ms
763 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 41% of them (55 requests) were addressed to the original 4cm.jp, 16% (21 requests) were made to Pbs.twimg.com and 10% (13 requests) were made to Graph.facebook.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain 4cm.jp.
Page size can be reduced by 760.3 kB (25%)
3.0 MB
2.3 MB
In fact, the total size of 4cm.jp 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.3 MB which makes up the majority of the site volume.
Potential reduce by 39.0 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 39.0 kB or 77% of the original size.
Potential reduce by 240.2 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. 4 Cm images are well optimized though.
Potential reduce by 180.1 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 180.1 kB or 67% of the original size.
Potential reduce by 301.0 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. 4cm.jp needs all CSS files to be minified and compressed as it can save up to 301.0 kB or 81% of the original size.
Number of requests can be reduced by 48 (40%)
119
71
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 4 Cm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.4cm.jp
1402 ms
style.css
1215 ms
visual-custom.css
712 ms
style.css
1482 ms
visual-custom.css
763 ms
styles.css
381 ms
prettyPhoto.css
947 ms
style.css
573 ms
shortcodes.css
703 ms
jetpack.css
1527 ms
jquery.min.js
66 ms
jquery.easing-min.js
773 ms
jquery.imagesloaded.min.js
1062 ms
jquery.masonry.min.js
1343 ms
jquery.devrama.slider.min.js
1511 ms
theme-import.min.js
1196 ms
jquery.prettyPhoto.js
1588 ms
front.js
1561 ms
bjqs.min.js
1660 ms
jquery.tablesorter.min.js
1913 ms
my_style.css
1699 ms
jquery.adrotate.clicktracker.js
1339 ms
jquery.form.min.js
1686 ms
scripts.js
1608 ms
script.min.js
1471 ms
devicepx-jetpack.js
4 ms
gprofiles.js
56 ms
wpgroho.js
1512 ms
e-201611.js
4 ms
wp-emoji-release.min.js
854 ms
bgt
1532 ms
0.gif
340 ms
logo4cm.png
292 ms
loading1.gif
377 ms
shop01_pc.jpg
872 ms
shop02_pc.jpg
568 ms
shop03_pc.jpg
588 ms
shop04_pc.jpg
887 ms
shop05_pc.jpg
1182 ms
image-2.jpg
1338 ms
banner_02-08.jpg
781 ms
banner_02.jpg
993 ms
banner_02-06.jpg
1176 ms
banner_02-04.jpg
993 ms
banner_02-09.jpg
1754 ms
loading2.gif
1172 ms
%EF%BD%94%EF%BC%96%E3%81%86tir1.png
2139 ms
%EF%BD%84%EF%BD%86%EF%BD%88%EF%BD%84%EF%BD%92image1.jpg
1526 ms
tyujytu.png
2122 ms
4cm-Stylist-Trial.jpg
1945 ms
CIMG3584.jpg
2633 ms
IMG_4485-e1449032604883.jpg
2593 ms
image29.jpg
2965 ms
CIMG3534-e1444748659280.jpg
2519 ms
IMG_0410-e1440650737202.jpg
2501 ms
facebook-bana.jpg
2329 ms
instagram.png
3283 ms
dpicons.svg
3024 ms
dpicons.woff
3618 ms
analytics.js
144 ms
widgets.js
147 ms
http%3A%2F%2Fwww.4cm.jp%2Fpost-3166%2F
135 ms
entry.count
500 ms
yql
637 ms
http%3A%2F%2Fwww.4cm.jp%2Fpost-3161%2F
174 ms
entry.count
496 ms
yql
750 ms
http%3A%2F%2Fwww.4cm.jp%2Fpost-3157%2F
170 ms
entry.count
488 ms
yql
944 ms
http%3A%2F%2Fwww.4cm.jp%2Fpost-1280%2F
157 ms
entry.count
488 ms
yql
1128 ms
http%3A%2F%2Fwww.4cm.jp%2Fpost-2039%2F
161 ms
entry.count
483 ms
yql
975 ms
http%3A%2F%2Fwww.4cm.jp%2Fpost-2028%2F
153 ms
entry.count
523 ms
yql
1061 ms
http%3A%2F%2Fwww.4cm.jp%2Fpost-1937%2F
150 ms
entry.count
630 ms
yql
1063 ms
http%3A%2F%2Fwww.4cm.jp%2Fpost-966%2F
177 ms
entry.count
629 ms
yql
1095 ms
http%3A%2F%2Fwww.4cm.jp%2Fnews%2Fnews-3000%2F
178 ms
entry.count
631 ms
yql
1246 ms
http%3A%2F%2Fwww.4cm.jp%2Fnews%2Fnews-2784%2F
179 ms
entry.count
638 ms
yql
1406 ms
http%3A%2F%2Fwww.4cm.jp%2Fnews%2Fnews-2222%2F
182 ms
entry.count
636 ms
yql
1732 ms
http%3A%2F%2Fwww.4cm.jp%2Fnews%2Fnews-1787%2F
178 ms
entry.count
721 ms
yql
1492 ms
http%3A%2F%2Fwww.4cm.jp%2Fnews%2Fnews-1164%2F
181 ms
entry.count
779 ms
yql
1329 ms
hovercard.css
77 ms
services.css
98 ms
g.gif
65 ms
collect
51 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
132 ms
slider-01.jpg
3470 ms
syndication
114 ms
630634584854499329
196 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
40 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
178 ms
dff960b19e46f406c840c1d3d8f4c7ae_normal.png
237 ms
Cd5rVy4XEAAmJu0.jpg:small
314 ms
Cd0aBr_UIAACbxl.jpg:small
442 ms
Cdzi9xBWIAEM-ru.jpg:small
437 ms
CdysIZFXEAAGOs1.jpg:small
433 ms
CdvQZkjWoAE04Fi.jpg:small
450 ms
CduZX5NWwAAXu1p.jpg:small
445 ms
CdtihnRXIAArkqJ.jpg:small
440 ms
CdqG0E-UIAA_hil.jpg:small
560 ms
CdpPxAZWIAEiaa_.jpg:small
525 ms
CdoY-F9WAAAvkPd.jpg:small
569 ms
Cdk9GvpW8AArdyu.jpg:small
573 ms
CdkGHG4VAAADu-9.jpg:small
525 ms
CdjPLGVVAAEWJfX.jpg:small
614 ms
Cdap_ytW0AQBzg8.jpg:small
724 ms
CdZzAnJW4AAhZaI.jpg:small
660 ms
CdY8LFzWAAASGAx.jpg:small
698 ms
CdVga0tWIAA62C1.jpg:small
593 ms
CdUpbMPXEAAcfOc.jpg:small
598 ms
CdTymaSUsAEEoN0.jpg:small
617 ms
CdQW1aaUkAEn3Xs.jpg:small
622 ms
jot
27 ms
slider-02.jpg
556 ms
4cm.jp 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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
4cm.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
Browser errors were logged to the console
4cm.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
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 4cm.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 4cm.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.
4cm.jp
Open Graph data is detected on the main page of 4 Cm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: