10.4 sec in total
543 ms
9 sec
808 ms
Click here to check amazing Obohsan content for Japan. Otherwise, check out these important facts you probably never knew about obohsan.com
法事・法要・葬儀・お葬式・お通夜でのお坊さんのお布施、戒名、僧侶、結婚式に関わる費用等のご相談はおぼうさんどっとこむへ。いくら?がわかる金額明示で安心を!見積書も領収書も完全発行!
Visit obohsan.comWe analyzed Obohsan.com page load time and found that the first response time was 543 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
obohsan.com performance score
name
value
score
weighting
Value16.7 s
0/100
10%
Value32.9 s
0/100
25%
Value24.3 s
0/100
10%
Value980 ms
28/100
30%
Value1.379
0/100
15%
Value30.1 s
0/100
10%
543 ms
3279 ms
665 ms
1195 ms
528 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 84% of them (120 requests) were addressed to the original Obohsan.com, 2% (3 requests) were made to Fonts.googleapis.com and 1% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Obohsan.com.
Page size can be reduced by 2.3 MB (27%)
8.5 MB
6.2 MB
In fact, the total size of Obohsan.com main page is 8.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.1 MB which makes up the majority of the site volume.
Potential reduce by 297.4 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. This page needs HTML code to be minified as it can gain 39.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 297.4 kB or 84% of the original size.
Potential reduce by 344.9 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. Obohsan images are well optimized though.
Potential reduce by 587.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 587.4 kB or 71% of the original size.
Potential reduce by 1.0 MB
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. Obohsan.com needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 86% of the original size.
Number of requests can be reduced by 96 (70%)
137
41
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Obohsan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 44 to 1 for CSS and as a result speed up the page load time.
obohsan.com
543 ms
obohsan.com
3279 ms
wp-emoji-release.min.js
665 ms
style.min.css
1195 ms
classic-themes.min.css
528 ms
animate.css
1651 ms
lvca-frontend.css
662 ms
icomoon.css
511 ms
all.min.css
1244 ms
bootstrap.min.css
1008 ms
front.css
1156 ms
slick.css
1174 ms
wpsisac-public.css
1194 ms
wpfront-scroll-top.min.css
1322 ms
style.css
1340 ms
slick.css
1364 ms
style.css
1419 ms
style.css
1487 ms
style.css
1507 ms
style.css
1535 ms
style.css
1536 ms
style.css
1594 ms
style.css
1651 ms
style.css
1672 ms
style.css
1705 ms
style.css
1706 ms
style.css
1769 ms
style.css
1813 ms
flexslider.css
1816 ms
style.css
1837 ms
style.css
1875 ms
style.css
1877 ms
dashicons.min.css
2120 ms
style.css
2307 ms
style.css
1980 ms
app.css
2002 ms
pum-site-styles.css
2044 ms
ajaxzip3.js
16 ms
jquery.min.js
1708 ms
jquery-migrate.min.js
1792 ms
jquery.waypoints.min.js
1662 ms
css
50 ms
bootstrap.min.css
52 ms
jquery-3.1.0.js
47 ms
popper.min.js
45 ms
bootstrap.min.js
61 ms
239c643321.js
46 ms
semantic.min.js
57 ms
jquery-migrate-3.0.0.js
48 ms
0cf69cbed7.js
59 ms
style.css
1898 ms
custom.css
1385 ms
owl.carousel.min.css
1275 ms
owl.theme.default.min.css
1177 ms
lvca-frontend.min.js
1164 ms
popper.min.js
1282 ms
bootstrap.min.js
1232 ms
front.js
1163 ms
accordion.min.js
1164 ms
slick.min.js
1203 ms
js
57 ms
js
127 ms
addtoany.min.css
1286 ms
jquery.stats.min.js
1223 ms
odometer.min.js
1161 ms
piechart.min.js
1164 ms
posts-carousel.min.js
1194 ms
spacer.min.js
1201 ms
services.min.js
1212 ms
stats-bar.min.js
1160 ms
tabs.min.js
1175 ms
jquery.flexslider.min.js
1165 ms
testimonials.min.js
1195 ms
isotope.pkgd.min.js
1201 ms
imagesloaded.pkgd.min.js
1201 ms
portfolio.min.js
1162 ms
index.js
1202 ms
calender_disable.js
1170 ms
owl.carousel.min.js
1293 ms
senderjs.js
1288 ms
regenerator-runtime.min.js
1189 ms
wp-polyfill.min.js
1169 ms
css
17 ms
hooks.min.js
1140 ms
i18n.min.js
1137 ms
jquery.form.min.js
1184 ms
wpfront-scroll-top.min.js
1158 ms
core.min.js
1132 ms
pum-site-scripts.js
1173 ms
mobile-detect.min.js
1009 ms
hoverIntent.min.js
1027 ms
maxmegamenu.js
1131 ms
slick.min.js
1089 ms
wpsisac-public.js
1003 ms
scripts.js
1065 ms
imageMapResizer.min.js
1081 ms
sdk.js
43 ms
css
30 ms
sdk.js
5 ms
130 ms
cropped-cropped-logo_head6.png
589 ms
header_freedial.png
589 ms
banner_99.png
589 ms
shiryo5.png
589 ms
toiawase5.png
663 ms
slider5-1024x461.png
2215 ms
202408_obonpc.png
1382 ms
%E6%B3%95%E8%A6%81%E6%96%BD%E8%A8%AD%E3%82%B9%E3%83%A9%E3%82%A4%E3%83%80%E3%83%BC-1024x476.jpg
890 ms
box_011.png
803 ms
reason_00.png
1086 ms
box_03.png
826 ms
box_04.png
912 ms
07_obohsan.png
1135 ms
0605_obohsan_sp_middle.png
1056 ms
manabiya_cl.png
1083 ms
soudan_cl.png
1283 ms
houyou_shisetsu.png
1284 ms
stuff_cl.png
1284 ms
ayumi_bn_pc.jpg
1467 ms
ayumi_bn_sp.jpg
1460 ms
voice_0823.png
1519 ms
voice_sp0823.png
1335 ms
logo_0824-300x108.png
1452 ms
fa-solid-900.ttf
1663 ms
widgets.js
16 ms
fa-regular-400.ttf
1672 ms
1.png
1489 ms
manga_01-F.jpg
2976 ms
manga_02-F.jpg
3067 ms
sp_reason3.png
1617 ms
sp_reason2.png
1664 ms
sp_reason1.png
1742 ms
60_persent-1.png
1641 ms
IMG_5888-scaled.jpg
1827 ms
15.jpg
1747 ms
matizemi.jpg
1980 ms
ajax-loader.gif
1854 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
37 ms
settings
221 ms
analytics.js
96 ms
collect
12 ms
collect
13 ms
print.css
172 ms
obohsan.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
[aria-*] attributes do not have valid values
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
obohsan.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
obohsan.com 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 Obohsan.com 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 Obohsan.com 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.
obohsan.com
Open Graph data is detected on the main page of Obohsan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: