8.9 sec in total
614 ms
7.4 sec
792 ms
Welcome to tokyogobyo.jp homepage info - get ready to check Tokyogobyo best content right away, or after learning these important things about tokyogobyo.jp
東京都内の納骨堂|荒川区・足立区・北区を中心に5000組以上のご家族の大切な場所として、宗派かかわらず日々お墓参り頂いております。永代供養や墓じまい・改葬も承ります。<駅近>町屋駅から徒歩3分・3路線利用可能な好アクセス。
Visit tokyogobyo.jpWe analyzed Tokyogobyo.jp page load time and found that the first response time was 614 ms and then it took 8.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.
tokyogobyo.jp performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value8.2 s
2/100
25%
Value14.3 s
1/100
10%
Value15,660 ms
0/100
30%
Value0.057
98/100
15%
Value22.7 s
1/100
10%
614 ms
1215 ms
57 ms
69 ms
176 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 52% of them (27 requests) were addressed to the original Tokyogobyo.jp, 10% (5 requests) were made to Cdn.jsdelivr.net and 10% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Tokyogobyo.jp.
Page size can be reduced by 107.9 kB (4%)
2.8 MB
2.7 MB
In fact, the total size of Tokyogobyo.jp main page is 2.8 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. 60% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 54.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. 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 54.1 kB or 76% of the original size.
Potential reduce by 43.0 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. Tokyogobyo images are well optimized though.
Potential reduce by 374 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 10.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. Tokyogobyo.jp needs all CSS files to be minified and compressed as it can save up to 10.4 kB or 47% of the original size.
Number of requests can be reduced by 18 (37%)
49
31
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokyogobyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
tokyogobyo.jp
614 ms
www.tokyogobyo.jp
1215 ms
slick.css
57 ms
slick-theme.css
69 ms
main.css
176 ms
analytics.js
74 ms
jquery.min.js
62 ms
wp-embed.min.js
345 ms
slick.min.js
71 ms
plan.css
337 ms
tag.js
429 ms
gtm.js
497 ms
head-logo.png
577 ms
login.png
576 ms
top_slide.jpg
3487 ms
slide2.jpg
1443 ms
login1.png
950 ms
main-logo.png
1138 ms
cloud.jpg
1310 ms
contents1-pc.png
1664 ms
contents2-pc.png
1284 ms
%E3%82%B3%E3%83%AD%E3%83%8A%E3%81%94%E8%A6%8B%E5%AD%A6%E3%83%90%E3%83%8A%E3%83%BC.jpg
1494 ms
%E6%9C%AC%E9%A4%A8%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6.jpg
1456 ms
%E3%82%88%E3%81%8F%E3%81%82%E3%82%8B%E8%B3%AA%E5%95%8F%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6.jpg
1495 ms
%E3%83%90%E3%83%8A%E3%83%BC%E7%94%A8.jpg
1783 ms
%E6%B0%B8%E4%BB%A3%E4%BE%9B%E9%A4%8A%E5%A2%93%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6.jpg
1625 ms
%E3%81%8A%E5%A2%93%E3%81%AE%E3%81%8A%E5%BC%95%E8%B6%8A%E3%81%97.jpg
1662 ms
%E5%90%8D%E7%A7%B0%E6%9C%AA%E8%A8%AD%E5%AE%9A-1-1.jpg
2182 ms
message-back.jpg
1959 ms
honbou.png
1840 ms
inage.png
1840 ms
ruri.png
1952 ms
fb.png
2027 ms
collect
116 ms
ajax-loader.gif
69 ms
contents3-pc.png
1819 ms
slick.woff
54 ms
tag
801 ms
ytag.js
906 ms
js
56 ms
js
33 ms
js
66 ms
conversion_async.js
58 ms
js
64 ms
collect
46 ms
86 ms
128 ms
collect
68 ms
65 ms
23 ms
23 ms
18 ms
tokyogobyo.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
Links do not have a discernible name
tokyogobyo.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
General
Impact
Issue
Detected JavaScript libraries
tokyogobyo.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 Tokyogobyo.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 Tokyogobyo.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.
tokyogobyo.jp
Open Graph description is not detected on the main page of Tokyogobyo. 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: