Tools & Wizards About Us
gojyokuru.net screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

gojyokuru.net

互助会のごじょクル：公式

Page Load Speed

7.6 sec in total

First Response

539 ms

Resources Loaded

6.5 sec

Page Rendered

565 ms

gojyokuru.net screenshot

About Website

Visit gojyokuru.net now to see the best up-to-date Gojyokuru content for Japan and also check out these interesting facts you probably never knew about gojyokuru.net

冠婚葬祭は互助会のごじょクルにお任せ下さい。葬儀や婚礼などの生涯のセレモニーの費用のご相談や、お見積、斎場や結婚式場の検索もできます。

Visit gojyokuru.net

Key Findings

We analyzed Gojyokuru.net page load time and found that the first response time was 539 ms and then it took 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.

Performance Metrics

gojyokuru.net performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value23.9 s

0/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.26

47/100

15%

TTI (Time to Interactive)

Value14.1 s

10/100

10%

Network Requests Diagram

gojyokuru.net

539 ms

www.gojyokuru.net

1301 ms

gtm.js

78 ms

css2

35 ms

slick.css

22 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 65% of them (69 requests) were addressed to the original Gojyokuru.net, 4% (4 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Gojyokuru.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 194.0 kB (37%)

Content Size

524.6 kB

After Optimization

330.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gojyokuru.net main page is 524.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 226.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 34.2 kB

  • Original 42.2 kB
  • After minification 33.8 kB
  • After compression 7.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.3 kB, which is 20% 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 34.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 226.8 kB
  • After minification 226.8 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. Gojyokuru images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 116.7 kB

  • Original 202.4 kB
  • After minification 201.0 kB
  • After compression 85.6 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 116.7 kB or 58% of the original size.

CSS Optimization

-81%

Potential reduce by 43.1 kB

  • Original 53.2 kB
  • After minification 52.9 kB
  • After compression 10.2 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. Gojyokuru.net needs all CSS files to be minified and compressed as it can save up to 43.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (42%)

Requests Now

97

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gojyokuru. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

gojyokuru.net

gojyokuru.net

539 ms

www.gojyokuru.net

www.gojyokuru.net

1301 ms

gtm.js

gtm.js

78 ms

css2

css2

35 ms

slick.css

slick.css

22 ms

common.min.css

common.min.css

510 ms

top.min.css

top.min.css

744 ms

logo.svg

logo.svg

668 ms

online.png

online.png

678 ms

contact.png

contact.png

679 ms

js

js

59 ms

analytics.js

analytics.js

24 ms

destination

destination

210 ms

s_retargeting.js

s_retargeting.js

705 ms

lpcv.js

lpcv.js

948 ms

segmentation.js

segmentation.js

258 ms

fmlp.js

fmlp.js

208 ms

maftag.js

maftag.js

1162 ms

ytag.js

ytag.js

734 ms

lt.js

lt.js

205 ms

collect

collect

157 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

752 ms

base.js

base.js

370 ms

common.js

common.js

518 ms

common.js

common.js

526 ms

slick.min.js

slick.min.js

47 ms

top.js

top.js

527 ms

collect

collect

75 ms

online-main_pc.png

online-main_pc.png

766 ms

sougi-main_pc.png

sougi-main_pc.png

767 ms

sougi-btn.png

sougi-btn.png

698 ms

celmo-main.png

celmo-main.png

718 ms

celmo-lead.png

celmo-lead.png

717 ms

main-ttl_pc.png

main-ttl_pc.png

879 ms

section01-img_pc.svg

section01-img_pc.svg

1066 ms

link1_pc.png

link1_pc.png

887 ms

link2_pc.png

link2_pc.png

941 ms

link3_pc.png

link3_pc.png

945 ms

link4_pc.png

link4_pc.png

947 ms

gojyokai01.svg

gojyokai01.svg

1059 ms

gojyokai02.svg

gojyokai02.svg

1072 ms

gojyokai03.svg

gojyokai03.svg

1133 ms

illust04.svg

illust04.svg

1140 ms

logo_01.svg

logo_01.svg

1125 ms

logo_02.svg

logo_02.svg

1239 ms

logo_03.svg

logo_03.svg

1245 ms

logo_04.svg

logo_04.svg

1247 ms

logo_05.svg

logo_05.svg

1304 ms

logo_06.svg

logo_06.svg

1324 ms

logo_07.svg

logo_07.svg

1331 ms

logo_08.svg

logo_08.svg

1418 ms

logo_09.svg

logo_09.svg

1425 ms

logo_10.svg

logo_10.svg

1423 ms

logo_11.svg

logo_11.svg

1483 ms

err.gif

err.gif

700 ms

cnt

cnt

732 ms

logo_12.svg

logo_12.svg

1344 ms

mieruca-hm.js

mieruca-hm.js

16 ms

logo_13.svg

logo_13.svg

1190 ms

logo_14.svg

logo_14.svg

1258 ms

logo_15.svg

logo_15.svg

1262 ms

logo_16.svg

logo_16.svg

1242 ms

css2

css2

17 ms

online.svg

online.svg

1255 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

77 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

221 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

224 ms

o-0XIpIxzW5b-RxT-6A8jWAtCp-cUW1CPA.ttf

o-0XIpIxzW5b-RxT-6A8jWAtCp-cUW1CPA.ttf

200 ms

fbds.js

fbds.js

12 ms

document.svg

document.svg

1196 ms

gojyokai-search.svg

gojyokai-search.svg

1194 ms

sougi-search.svg

sougi-search.svg

1257 ms

kekkon-search.svg

kekkon-search.svg

1071 ms

menu.svg

menu.svg

1070 ms

arrow.svg

arrow.svg

1127 ms

beacon.html

beacon.html

79 ms

bg_dot.svg

bg_dot.svg

3617 ms

num01.svg

num01.svg

1144 ms

icon01.svg

icon01.svg

1195 ms

tap.php

tap.php

38 ms

Pug

Pug

43 ms

set

set

228 ms

pixel

pixel

48 ms

num02.svg

num02.svg

1084 ms

pixel

pixel

14 ms

sd

sd

8 ms

pixel

pixel

15 ms

icon02.svg

icon02.svg

1078 ms

bounce

bounce

11 ms

sync

sync

718 ms

report

report

747 ms

num03.svg

num03.svg

1082 ms

icon03.svg

icon03.svg

1157 ms

num04.svg

num04.svg

1195 ms

icon04.svg

icon04.svg

1081 ms

arrow-circle.svg

arrow-circle.svg

1074 ms

illust01.svg

illust01.svg

1129 ms

line-ttl.svg

line-ttl.svg

1165 ms

illust02.svg

illust02.svg

1187 ms

illust03.svg

illust03.svg

1183 ms

map.svg

map.svg

1267 ms

arrow-circle.svg

arrow-circle.svg

1135 ms

arrow.svg

arrow.svg

1235 ms

online.svg

online.svg

1197 ms

document.svg

document.svg

1180 ms

sync

sync

264 ms

Accessibility Review

gojyokuru.net accessibility score

92

Accessibility Issues

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

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

gojyokuru.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

gojyokuru.net SEO score

98

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gojyokuru.net 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 Gojyokuru.net 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.

Social Sharing Optimization

gojyokuru.net

Open Graph description is not detected on the main page of Gojyokuru. 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: