5.8 sec in total
1.6 sec
3.5 sec
651 ms
Welcome to guideme.jp homepage info - get ready to check Guideme best content for Japan right away, or after learning these important things about guideme.jp
今話題のニュース・画像・動画・口コミが一発で分かります。まとめ情報ならガイドミー!
Visit guideme.jpWe analyzed Guideme.jp page load time and found that the first response time was 1.6 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
guideme.jp performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value7.7 s
3/100
25%
Value12.5 s
3/100
10%
Value1,110 ms
23/100
30%
Value0.292
41/100
15%
Value13.4 s
11/100
10%
1582 ms
336 ms
334 ms
347 ms
363 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 27% of them (28 requests) were addressed to the original Guideme.jp, 20% (21 requests) were made to Pbs.twimg.com and 16% (16 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Guideme.jp.
Page size can be reduced by 465.8 kB (20%)
2.3 MB
1.9 MB
In fact, the total size of Guideme.jp main page is 2.3 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 69.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. 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 69.2 kB or 76% of the original size.
Potential reduce by 14.4 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. Guideme images are well optimized though.
Potential reduce by 285.9 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 285.9 kB or 77% of the original size.
Potential reduce by 96.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. Guideme.jp needs all CSS files to be minified and compressed as it can save up to 96.3 kB or 83% of the original size.
Number of requests can be reduced by 47 (47%)
101
54
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guideme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
guideme.jp
1582 ms
bootstrap.min.css
336 ms
bootstrap-responsive.css
334 ms
jquery.bubblepopup.v2.3.1.css
347 ms
guideme.css
363 ms
take.css
370 ms
jquery.simplyscroll-1.0.4.css
382 ms
trvfeed.php
543 ms
jquery.js
829 ms
bootstrap-collapse.js
318 ms
pc.js
336 ms
jquery.bubblepopup.v2.3.1.min.js
445 ms
bootstrap-dropdown.js
445 ms
bootstrap-transition.js
444 ms
bootstrap-modal.js
480 ms
bootstrap-tooltip.js
505 ms
jquery.cookie.js
536 ms
news.js
554 ms
jquery.simplyscroll.min.js
556 ms
jquery.raty.min.js
643 ms
raku.js
677 ms
captify.js
717 ms
jquery-contained-sticky-scroll.js
739 ms
jquery.lazyload.js
740 ms
ga.js
46 ms
all.js
247 ms
images
65 ms
images
69 ms
images
53 ms
XszsqxK+jY4bpKAHxBnVr3++lWPWn19NibS5AWkMO4FCxZjVlSAtqCtJ0TCSLfXbe5u8+pX9RcSQi4Ncvz2bjUWFucXqQ0dc4Dxyk2hCxwzmliGDWFsvxEmHnpZvZoGD
572 ms
qQLCcDg5hxPRnVJSnvTSZfwqS0SLyxt1nx8zDalu
565 ms
rDa5VBGGznPBTLm9aUCrmFoLuW88H27DncQzmDdc3UCVr39Fy20l5OVnGeNA2EbIK8gRnzt1clx8L4CZkbxJhw==
579 ms
oHQow0Scfa+LeMKU0fJcJkHBWweSeRb4Z9bMFsqM5+2XTiNPjw9G+jU1NBvh378VRjbld+yUypLOO2wF5OGZ9g==
586 ms
G9bkBIqkbk4nD3lkdjguEH2FErazcssZPXujum3E+Z3Z+elfiLzMiKsEPyJtnQxsQmU
585 ms
CYBkNx4cdFntrzMpeg5VYIOOap2k5QuL+mDN3V7TXrA=
888 ms
qr.png
605 ms
wait2.gif
704 ms
totop.png
707 ms
__utm.gif
12 ms
collect
57 ms
136986.jpg
1408 ms
4896.jpg
728 ms
32250.jpg
1445 ms
8401.jpg
1442 ms
40926.jpg
1437 ms
glyphicons-halflings.png
554 ms
widgets.js
18 ms
147 ms
xd_arbiter.php
117 ms
xd_arbiter.php
241 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
52 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
51 ms
star-on.png
191 ms
syndication
114 ms
611786994444701696
196 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
20 ms
page.php
289 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
4 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
6 ms
lmlci9qr7zix0kny0a7j_normal.png
114 ms
CcYxyQcUEAABMZM.jpg:small
180 ms
CcYwo9CUMAA1IFa.jpg:small
147 ms
CcYvfvBUYAEGvS_.jpg:small
150 ms
CcYuWhZUsAAAjRH.jpg:small
163 ms
CcYtNUyUMAEYhFu.jpg:small
149 ms
CcYsERzUYAIJx3M.jpg:small
147 ms
CcYq66nUAAAlVxY.jpg:small
178 ms
CcYpxjZUUAEc7qN.jpg:small
178 ms
CcYooUpUAAA03u3.jpg:small
178 ms
CcYnfMtUcAAR74i.jpg:small
191 ms
CcYmWA1VAAEo-0o.jpg:small
208 ms
CcYlMpmUUAEjj4g.jpg:small
219 ms
CcYi6tMUUAELh5h.jpg:small
221 ms
CcYhw4dUsAAsylA.jpg:small
233 ms
CcYeVLcUsAAchqs.jpg:small
214 ms
CcYa5rzUkAArZmx.jpg:small
242 ms
CcYWU_1UMAIeDN9.jpg:small
274 ms
CcYVLbcUUAETGpe.jpg:small
256 ms
CcYUCHOUUAEHdRy.jpg:small
254 ms
CcYS4w6VIAE5V8H.jpg:small
415 ms
lT4BYBcBnt6.css
157 ms
ry5HQcHFiDn.css
177 ms
UF-aMojPZfI.css
198 ms
_rx8naC75Dy.js
247 ms
t-KLv3gqZy0.js
224 ms
uLtKx7ldlvR.js
264 ms
xoyOB9tkUFt.js
218 ms
wyIfBc7KBcg.js
276 ms
486726_429178953785129_297683685_n.png
117 ms
safe_image.php
266 ms
safe_image.php
423 ms
safe_image.php
424 ms
safe_image.php
340 ms
safe_image.php
342 ms
wL6VQj7Ab77.png
78 ms
CSXXCvknpgK.png
78 ms
7NEHk19WerA.png
77 ms
lRyN50VcaFW.js
27 ms
jot.html
16 ms
R9a_DtVRZgv.js
18 ms
cUDgRFxaoIk.js
19 ms
0JBr1QHp8Gi.js
21 ms
kDOzhTr2W91.js
19 ms
guideme.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
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.
guideme.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
guideme.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
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 Guideme.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 Guideme.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.
guideme.jp
Open Graph description is not detected on the main page of Guideme. 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: