9 sec in total
678 ms
4.7 sec
3.6 sec
Visit pochilog.jp now to see the best up-to-date Pochilog content for Japan and also check out these interesting facts you probably never knew about pochilog.jp
EOS R6II・GR III・α7IIIの実体験お散歩カメラブログ。
Visit pochilog.jpWe analyzed Pochilog.jp page load time and found that the first response time was 678 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pochilog.jp performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.8 s
30/100
25%
Value14.0 s
1/100
10%
Value3,130 ms
2/100
30%
Value0.225
55/100
15%
Value26.4 s
0/100
10%
678 ms
1050 ms
402 ms
78 ms
160 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 59% of them (63 requests) were addressed to the original Pochilog.jp, 11% (12 requests) were made to Googleads.g.doubleclick.net and 6% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Pochilog.jp.
Page size can be reduced by 326.4 kB (12%)
2.7 MB
2.4 MB
In fact, the total size of Pochilog.jp main page is 2.7 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 109.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 109.7 kB or 79% of the original size.
Potential reduce by 11.1 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. Pochilog images are well optimized though.
Potential reduce by 190.3 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 190.3 kB or 18% of the original size.
Potential reduce by 15.3 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. Pochilog.jp needs all CSS files to be minified and compressed as it can save up to 15.3 kB or 21% of the original size.
Number of requests can be reduced by 57 (58%)
99
42
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pochilog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
pochilog.jp
678 ms
pochilog.jp
1050 ms
21gl5.css
402 ms
vegas.min.css
78 ms
cvn3rxt.css
160 ms
21gl5.css
698 ms
21gl5.css
702 ms
js
124 ms
adsbygoogle.js
108 ms
api.js
90 ms
wpp.min.js
526 ms
page.js
80 ms
jquery.min.js
858 ms
jquery-migrate.min.js
596 ms
addtoany.min.js
600 ms
event-tracking.js
858 ms
jquery-3.6.3.min.js
73 ms
pochiloghead.js
264 ms
jquery.cookie.min.js
859 ms
vegas.min.js
858 ms
vegas-setting.js
939 ms
jquery.flexslider.js
939 ms
hooks.min.js
940 ms
i18n.min.js
958 ms
index.js
1046 ms
index.js
1047 ms
front.min.js
1048 ms
wp-polyfill.min.js
1100 ms
index.js
1101 ms
prism.js
1299 ms
clipboard.min.js
1196 ms
hcb_script.js
1230 ms
e-202433.js
62 ms
jquery.touchwipe.min.js
1213 ms
purify.min.js
1220 ms
panzoom.min.js
1220 ms
jquery.lightbox.js
1398 ms
base.js
1389 ms
p.css
22 ms
1.JiBnMqyl6S.gif
687 ms
google_eyecatch.jpg
688 ms
logo.png
720 ms
search.svg
762 ms
01_feecap_assoc_central_lp_hero_dtmb_1070x260_b-500x121.jpg
925 ms
41A4725-500x333.jpg
1301 ms
41A3951-500x333.jpg
1088 ms
11_o-500x375.jpg
1089 ms
R002423-500x333.jpg
1122 ms
41A1414-500x333.jpg
1121 ms
IMG_2085-500x375.jpg
1298 ms
01_PENTAX17-500x359.jpeg
1301 ms
rf35-f14lv-01-500x310.jpeg
1301 ms
41A0786-500x333.jpg
1471 ms
Lumix_S9_picture_stphoto_001-500x381.jpg
1202 ms
03-pc-500x357.jpeg
1294 ms
IMG_1650-500x375.jpg
1469 ms
p20240515a-500x333.jpg
1299 ms
fa-v4compatibility.ttf
1493 ms
show_ads_impl.js
128 ms
fa-regular-400.ttf
1431 ms
fa-brands-400.ttf
1499 ms
fa-solid-900.ttf
1503 ms
recaptcha__en.js
37 ms
matomo.js
1409 ms
IMG_1535-500x375.jpg
1455 ms
IMG_1465-500x375.jpg
1700 ms
Rollei35AF-01-s_34de427b-1c30-4e69-a82f-695bd04c2dd5.jpg-375x500.webp
1465 ms
DSC_0568-500x334.jpg
1439 ms
zrt_lookup.html
35 ms
ads
398 ms
41A6311-500x333.jpg
1657 ms
ads
498 ms
41A6286-500x333.jpg
1420 ms
41A6278-500x333.jpg
1464 ms
41A6136-500x333.jpg
1494 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2024-03-13-11.13.55-500x368.png
1743 ms
IMG_0919-500x333.jpg
1564 ms
sm.25.html
15 ms
eso.D0Uc7kY6.js
25 ms
css2
33 ms
reactive_library.js
109 ms
ads
294 ms
ads
290 ms
ads
346 ms
ads
465 ms
ads
384 ms
ads
419 ms
ads
454 ms
load_preloaded_resource.js
61 ms
abg_lite.js
61 ms
s
191 ms
window_focus.js
73 ms
qs_click_protection.js
75 ms
ufs_web_display.js
50 ms
bd0892cabc977a7e24fe92843da0e49e.js
48 ms
fullscreen_api_adapter.js
174 ms
interstitial_ad_frame.js
174 ms
icon.png
185 ms
feedback_grey600_24dp.png
47 ms
settings_grey600_24dp.png
46 ms
css
84 ms
css
87 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
20 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
36 ms
font
39 ms
5ukJAjAsZg1jLVgbZZP3i3KUOHFWqH5cQ5Ck9k2x6xY.js
5 ms
matomo.php
611 ms
pochilog.jp accessibility score
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
Links do not have a discernible name
pochilog.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pochilog.jp SEO score
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 Pochilog.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 Pochilog.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.
pochilog.jp
Open Graph data is detected on the main page of Pochilog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: