7.2 sec in total
543 ms
5.3 sec
1.3 sec
Visit ohnoya.co.jp now to see the best up-to-date Ohnoya content for Japan and also check out these interesting facts you probably never knew about ohnoya.co.jp
メモリアルアートの大野屋は、1939年に石材店として創業以来、葬儀、墓石、仏壇、手元供養など、仏事に関する安心のサービスをご提供し、お客様と供に成長するという姿勢で歩み続けています。
Visit ohnoya.co.jpWe analyzed Ohnoya.co.jp page load time and found that the first response time was 543 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ohnoya.co.jp performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value10.1 s
0/100
25%
Value4.6 s
71/100
10%
Value1,780 ms
10/100
30%
Value0.481
17/100
15%
Value13.4 s
11/100
10%
543 ms
1183 ms
70 ms
109 ms
174 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 79% of them (74 requests) were addressed to the original Ohnoya.co.jp, 5% (5 requests) were made to Googletagmanager.com and 3% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ohnoya.co.jp.
Page size can be reduced by 409.2 kB (9%)
4.6 MB
4.2 MB
In fact, the total size of Ohnoya.co.jp main page is 4.6 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. 65% of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 41.9 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 8.6 kB, which is 17% 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 41.9 kB or 81% of the original size.
Potential reduce by 253.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. Ohnoya images are well optimized though.
Potential reduce by 68.0 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 68.0 kB or 18% of the original size.
Potential reduce by 45.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. Ohnoya.co.jp needs all CSS files to be minified and compressed as it can save up to 45.4 kB or 84% of the original size.
Number of requests can be reduced by 16 (17%)
92
76
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ohnoya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
ohnoya.co.jp
543 ms
www.ohnoya.co.jp
1183 ms
gtm.js
70 ms
gtm.js
109 ms
adsbygoogle.js
174 ms
reset.css
259 ms
common.css
451 ms
style.css
682 ms
ohnoya_ga.js
685 ms
jquery.min.js
1044 ms
main.js
683 ms
picturefill.min.js
683 ms
368e176da7.js
105 ms
js
120 ms
analytics.js
113 ms
js
111 ms
show_ads_impl.js
463 ms
js
209 ms
d9csbe9v99
379 ms
collect
259 ms
bnr_line_subbnr.png
1246 ms
logo.png
230 ms
logo_sp.png
415 ms
icon_fb.png
433 ms
icon_x.png
424 ms
ttl_grave.png
434 ms
ttl_funeral.png
755 ms
ttl_altar.png
754 ms
ttl_memorialservice.png
760 ms
ttl_hojin.png
761 ms
ttl_telephone.png
761 ms
ttl_notice.png
782 ms
ttl_shop.png
784 ms
ttl_shop_list.png
775 ms
ttl_company.png
833 ms
ttl_corporatemesage.png
837 ms
ttl_corporatemesage_sp.png
836 ms
ttl_presidentmessage.png
957 ms
ttl_presidentmessage_sp.png
974 ms
ttl_companyoverview.png
976 ms
ttl_companyoverview_sp.png
1037 ms
ttl_philosophy.png
1043 ms
ttl_philosophy_sp.png
1038 ms
ttl_history.png
1136 ms
ttl_history_sp.png
1165 ms
ttl_contact.png
1168 ms
ttl_contact_sp.png
1243 ms
icon_pagetop.png
1238 ms
f_tel.png
1244 ms
f_tel-pc.png
1315 ms
f_btn1.png
1357 ms
f_btn1-pc.png
1357 ms
clarity.js
191 ms
f_btn2.png
1218 ms
f_btn2-pc.png
1223 ms
logo_mao.png
1224 ms
collect
188 ms
arrow_r.png
1245 ms
service01.jpg
1538 ms
zrt_lookup.html
56 ms
ads
123 ms
service01_on.jpg
1316 ms
new-window.png
1224 ms
service02.jpg
1846 ms
service02_on.jpg
1407 ms
ytag.js
701 ms
service03.jpg
1312 ms
service03_on.jpg
1286 ms
service04.jpg
1521 ms
service04_on.jpg
1284 ms
service06.jpg
1521 ms
service06_on.jpg
1426 ms
service07.jpg
1840 ms
service07_on.jpg
1465 ms
arrow_g.png
1587 ms
bg_shop_list.jpg
1808 ms
bg_shop_list_on.png
1839 ms
company01.jpg
1633 ms
company01_on.jpg
1521 ms
company02.jpg
1578 ms
company02_on.jpg
1687 ms
company03.jpg
1810 ms
company03_on.jpg
1690 ms
company04.jpg
1961 ms
company04_on.jpg
1707 ms
company05.jpg
1689 ms
company05_on.jpg
1713 ms
company06.jpg
1671 ms
company06_on.jpg
1804 ms
kv_pc.jpg
1796 ms
ttl_service.png
1729 ms
sodar
71 ms
sodar2.js
17 ms
c.gif
8 ms
ohnoya.co.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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
ohnoya.co.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ohnoya.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ohnoya.co.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 Ohnoya.co.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.
ohnoya.co.jp
Open Graph description is not detected on the main page of Ohnoya. 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: