Tools & Wizards About Us

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

gifu-obake.net

岐阜柳ケ瀬お化け屋敷『恐怖の細道』～消えた子どもたち～

Page Load Speed

3.6 sec in total

First Response

740 ms

Resources Loaded

2.6 sec

Page Rendered

304 ms

About Website

Welcome to gifu-obake.net homepage info - get ready to check Gifu Obake best content right away, or after learning these important things about gifu-obake.net

岐阜・柳ケ瀬商店街のまちおこし企画として生まれた、お化け屋敷「恐怖の細道」が今年、パワーアップして復活！突如、岐阜で巻き起こった謎の連続失踪事件の真相は？昭和最大の都市伝説が、令和元年に再び目覚める…。

Visit gifu-obake.net

Key Findings

We analyzed Gifu-obake.net page load time and found that the first response time was 740 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

gifu-obake.net performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value20.1 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value1,530 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value1.05

2/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

gifu-obake.net

740 ms

common.css

317 ms

styles.css

335 ms

header.jpg

1160 ms

spacer.gif

169 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 36% of them (21 requests) were addressed to the original Gifu-obake.net, 33% (19 requests) were made to Pbs.twimg.com and 12% (7 requests) were made to O.twimg.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Gifu-obake.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.9 kB (5%)

Content Size

1.6 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gifu-obake.net main page is 1.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. 55% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 5.0 kB

  • Original 8.6 kB
  • After minification 8.1 kB
  • After compression 3.6 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 5.0 kB or 58% of the original size.

Image Optimization

-3%

Potential reduce by 45.8 kB

  • Original 1.6 MB
  • After minification 1.5 MB

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. Gifu Obake images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-83%

Potential reduce by 29.1 kB

  • Original 34.9 kB
  • After minification 34.1 kB
  • After compression 5.8 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. Gifu-obake.net needs all CSS files to be minified and compressed as it can save up to 29.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (14%)

Requests Now

57

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

gifu-obake.net accessibility score

73

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

gifu-obake.net best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

gifu-obake.net SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gifu-obake.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 Gifu-obake.net main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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