8.9 sec in total
583 ms
6.5 sec
1.8 sec
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 583 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.
tokyogobyo.jp performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value26.1 s
0/100
25%
Value15.0 s
1/100
10%
Value1,040 ms
25/100
30%
Value1.138
1/100
15%
Value19.9 s
2/100
10%
583 ms
1312 ms
97 ms
878 ms
57 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 83% of them (66 requests) were addressed to the original Tokyogobyo.jp, 5% (4 requests) were made to Unpkg.com and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Tokyogobyo.jp.
Page size can be reduced by 723.8 kB (4%)
17.1 MB
16.4 MB
In fact, the total size of Tokyogobyo.jp main page is 17.1 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. Only a small number of websites need less resources to load. Images take 16.8 MB which makes up the majority of the site volume.
Potential reduce by 60.5 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 60.5 kB or 80% of the original size.
Potential reduce by 570.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. Tokyogobyo images are well optimized though.
Potential reduce by 64.4 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 64.4 kB or 44% of the original size.
Potential reduce by 28.7 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 28.7 kB or 24% of the original size.
Number of requests can be reduced by 27 (37%)
73
46
The browser has sent 73 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 14 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
tokyogobyo.jp
583 ms
www.tokyogobyo.jp
1312 ms
gtm.js
97 ms
ytag.js
878 ms
destyle.css
57 ms
css2
61 ms
os-animation.min.css
192 ms
common.css
384 ms
each.css
531 ms
parts.css
529 ms
page.css
768 ms
jquery.min.js
45 ms
swiper-bundle.min.css
64 ms
lity.min.css
575 ms
index.css
574 ms
style.min.css
575 ms
dashicons.min.css
875 ms
xo-event-calendar.css
700 ms
jquery.matchHeight-min.js
50 ms
jquery.easing.min.js
60 ms
os-animation.min.js
762 ms
common.js
797 ms
page.js
833 ms
slick-theme.css
872 ms
slick.css
993 ms
slick.min.js
992 ms
swiper-bundle.min.js
71 ms
lity.min.js
992 ms
index.js
1026 ms
jquery.min.js
42 ms
comment-reply.min.js
1046 ms
ajax.js
1047 ms
swiper-bundle.min.css
54 ms
swiper-bundle.min.js
40 ms
header-logo00.svg
267 ms
header-btn01.svg
270 ms
header-btn02.svg
272 ms
header-btn03.svg
339 ms
header-logo00-sp.svg
343 ms
top-mv_01_bg.png
1046 ms
top-mv_01.png
1227 ms
top-mv_01_sp.png
1240 ms
top-mv_02_bg.png
1800 ms
top-mv_02.png
1292 ms
top-mv_02_sp.png
1733 ms
top-mv_03.png
1394 ms
top-mv_03_sp.png
1619 ms
top-mv_img_1.png
1433 ms
top-mv_img_1_sp.png
1483 ms
top-mv_btn_1@2x.png
1568 ms
top-mv_btn_2@2x.png
1626 ms
top-sec1_bg.png
1675 ms
top-sec1_img_1.png
1761 ms
top-sec2_bg.png
1810 ms
top-sec2_img_1.png
2012 ms
top-sec2_img_1_sp.png
1873 ms
ac89035c0b8b5113eae95df6dcb3c02c.jpg
1907 ms
4a8fe346b5241ec650d7c04d181925cf.jpg
1936 ms
6241ea4a81b6c965833ebc6f016a3013.jpg
1991 ms
nagoyaka_bg.png
2020 ms
nagoyaka_ttl.png
2064 ms
22289312_m.jpg
2278 ms
22cdce2b53f6b613293320b412445e34.jpg
2129 ms
28040607_l-scaled.jpg
2094 ms
28743145_m.jpg
2315 ms
22cdce2b53f6b613293320b412445e34.jpg
2118 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf
86 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf
146 ms
map01.svg
2140 ms
map01-sp.png
2153 ms
map02.png
2241 ms
footer-bg02.jpg
2259 ms
footer-logo.svg
2186 ms
footer-freedial-white.svg
2185 ms
footer-banner01.png
2179 ms
footer-banner02.png
2260 ms
footer-banner03.png
2275 ms
footer-banner04.png
1574 ms
footer-facebook.svg
1417 ms
top-mv_03_bg.png
1406 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
tokyogobyo.jp SEO score
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 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 data is detected on the main page of Tokyogobyo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: