10.8 sec in total
1.6 sec
8.5 sec
692 ms
Click here to check amazing PIGEON RECORDS content for Japan. Otherwise, check out these important facts you probably never knew about pigeon-records.jp
名古屋のレコードショップ PIGEON RECORDS のオンラインショッピングサイト。
Visit pigeon-records.jpWe analyzed Pigeon-records.jp page load time and found that the first response time was 1.6 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pigeon-records.jp performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value2.9 s
82/100
25%
Value4.4 s
74/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.5 s
98/100
10%
1592 ms
339 ms
352 ms
352 ms
361 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 97% of them (75 requests) were addressed to the original Pigeon-records.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Pigeon-records.jp.
Page size can be reduced by 48.7 kB (3%)
1.4 MB
1.4 MB
In fact, the total size of Pigeon-records.jp main page is 1.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. 30% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 25.7 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 25.7 kB or 76% of the original size.
Potential reduce by 2.8 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. PIGEON RECORDS images are well optimized though.
Potential reduce by 6.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 6.6 kB or 51% of the original size.
Potential reduce by 13.6 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. Pigeon-records.jp needs all CSS files to be minified and compressed as it can save up to 13.6 kB or 83% of the original size.
Number of requests can be reduced by 3 (4%)
76
73
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PIGEON RECORDS. 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.
pigeon-records.jp
1592 ms
main.css
339 ms
findchild.js
352 ms
tinyscrolling.js
352 ms
cart.js
361 ms
common.css
506 ms
urchin.js
7 ms
default.css
179 ms
back_body.gif
178 ms
back_main.gif
170 ms
header01.gif
182 ms
logo01.gif
174 ms
listvline01.gif
176 ms
groback_t.gif
339 ms
groback_b.gif
347 ms
gnavi-new.jpg
526 ms
gnavi-used.jpg
354 ms
gnavi-others.jpg
355 ms
gnavi-cart.jpg
362 ms
gnavi-search01.gif
507 ms
ttl_topics.gif
520 ms
img635_0923.jpg
1061 ms
img637_file.jpg
1064 ms
img630_file.jpg
1625 ms
img579_file.jpg
1225 ms
img636_file.jpg
1556 ms
img632_file.jpg
1266 ms
img633_file.jpg
1415 ms
img626_file.jpg
1773 ms
img631_file.jpg
1728 ms
ttl_new.gif
1443 ms
mrp852.jpg
1594 ms
btn_listen.gif
1618 ms
mrp15838.jpg
1729 ms
mrp8646.jpg
1770 ms
mrp8642.jpg
1793 ms
mrp8647.jpg
1804 ms
mrp8644.jpg
1897 ms
ttl_recommend.gif
1902 ms
mrp39849.jpg
1947 ms
mrp39830.jpg
6557 ms
mrp39762.jpg
1968 ms
mrp39690.jpg
1985 ms
__utm.gif
4 ms
mrp39778.jpg
2032 ms
mrp39780.jpg
1911 ms
mrp39779.jpg
1955 ms
mrp39759.jpg
1971 ms
mrp39560.jpg
1993 ms
mrp39598.jpg
2057 ms
mrp39637.jpg
1914 ms
mrp39553.jpg
1959 ms
mrp39678.jpg
1968 ms
mrp39643.jpg
1996 ms
mrp39597.jpg
2047 ms
mrp39543.jpg
1918 ms
mrp39441.jpg
1962 ms
mrp39532.jpg
1972 ms
mrp39445.jpg
1471 ms
mrp39475.jpg
1515 ms
mrp39512.jpg
1376 ms
mrp39410.jpg
1392 ms
mrp39327.jpg
1257 ms
mrp39329.jpg
1269 ms
mrp39162.jpg
1190 ms
mrp39358.jpg
1179 ms
mrp39289.jpg
1219 ms
mrp37862.jpg
1224 ms
mrp39243.jpg
1173 ms
mrp39260.jpg
1186 ms
mrp39292.jpg
1176 ms
mrp39280.jpg
1242 ms
mrp39277.jpg
1230 ms
mrp39310.jpg
1269 ms
mrp39232.jpg
1188 ms
mrp38932.jpg
1217 ms
back_footer.gif
1247 ms
pigeon-records.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
Form elements do not have associated labels
pigeon-records.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
pigeon-records.jp SEO score
EN
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pigeon-records.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Pigeon-records.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
pigeon-records.jp
Open Graph description is not detected on the main page of PIGEON RECORDS. 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: