Tools & Wizards About Us
urayasu-fan.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

urayasu-fan.com

浦安ファン.com| ディズニーリゾートがある都市型リゾートタウン・浦安の魅力を徹底解説！

Page Load Speed

9 sec in total

First Response

1.9 sec

Resources Loaded

4.7 sec

Page Rendered

2.3 sec

urayasu-fan.com screenshot

About Website

Visit urayasu-fan.com now to see the best up-to-date Urayasu Fan content and also check out these interesting facts you probably never knew about urayasu-fan.com

【ディズニーリゾートのある街、浦安】 なぜ浦安は住みやすい街ランキングでトップレベルなのか？ 浦安のこれからの都市計画や取り組みを分析し、未来の浦安の開発計画などをご紹介します！

Visit urayasu-fan.com

Key Findings

We analyzed Urayasu-fan.com page load time and found that the first response time was 1.9 sec and then it took 7.1 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

urayasu-fan.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.174

69/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

urayasu-fan.com

1942 ms

adsbygoogle.js

207 ms

analytics.js

285 ms

autotrack.js

284 ms

wp-emoji-release.min.js

253 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 73% of them (62 requests) were addressed to the original Urayasu-fan.com, 7% (6 requests) were made to Translate.googleapis.com and 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Urayasu-fan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 311.0 kB (29%)

Content Size

1.1 MB

After Optimization

764.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Urayasu-fan.com main page is 1.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. 60% of websites need less resources to load. Images take 549.1 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 55.2 kB

  • Original 73.0 kB
  • After minification 71.6 kB
  • After compression 17.8 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 55.2 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 37 B

  • Original 549.1 kB
  • After minification 549.1 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. Urayasu Fan images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 117.9 kB

  • Original 283.4 kB
  • After minification 274.6 kB
  • After compression 165.5 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 117.9 kB or 42% of the original size.

CSS Optimization

-81%

Potential reduce by 137.9 kB

  • Original 170.0 kB
  • After minification 141.6 kB
  • After compression 32.0 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. Urayasu-fan.com needs all CSS files to be minified and compressed as it can save up to 137.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (81%)

Requests Now

81

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

urayasu-fan.com

urayasu-fan.com

1942 ms

adsbygoogle.js

adsbygoogle.js

207 ms

analytics.js

analytics.js

285 ms

autotrack.js

autotrack.js

284 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

253 ms

style.min.css

style.min.css

422 ms

styles.css

styles.css

474 ms

font-awesome.min.css

font-awesome.min.css

417 ms

screen.min.css

screen.min.css

426 ms

whats-new.css

whats-new.css

425 ms

wpp.css

wpp.css

474 ms

style.css

style.css

594 ms

common.css

common.css

590 ms

ie.css

ie.css

622 ms

css

css

138 ms

font.css

font.css

571 ms

jquery.fs.boxer.css

jquery.fs.boxer.css

581 ms

pc.css

pc.css

605 ms

ja.css

ja.css

747 ms

addtoany.min.css

addtoany.min.css

753 ms

jquery.js

jquery.js

937 ms

addtoany.min.js

addtoany.min.js

759 ms

wpp.min.js

wpp.min.js

768 ms

element.js

element.js

285 ms

scripts.js

scripts.js

781 ms

front.min.js

front.min.js

920 ms

watermark.js

watermark.js

933 ms

navimenu.js

navimenu.js

1339 ms

slidenav.js

slidenav.js

1340 ms

rollover.js

rollover.js

1339 ms

thumbnail-image.js

thumbnail-image.js

1359 ms

jquery.fs.boxer.min.js

jquery.fs.boxer.min.js

1359 ms

boxer.js

boxer.js

1359 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1359 ms

slider.js

slider.js

1358 ms

core.min.js

core.min.js

1357 ms

widget.min.js

widget.min.js

1550 ms

position.min.js

position.min.js

1549 ms

tooltip.min.js

tooltip.min.js

1546 ms

tooltips.js

tooltips.js

1547 ms

linkposition.js

linkposition.js

1528 ms

imagesloaded.min.js

imagesloaded.min.js

1442 ms

ec.js

ec.js

18 ms

linkid.js

linkid.js

19 ms

collect

collect

4 ms

collect

collect

63 ms

masonry.min.js

masonry.min.js

1584 ms

jquery.masonry.min.js

jquery.masonry.min.js

1390 ms

masonry-widget.js

masonry-widget.js

1400 ms

footer-fixed.js

footer-fixed.js

1389 ms

pagescroll.js

pagescroll.js

1350 ms

wp-embed.min.js

wp-embed.min.js

1346 ms

page.js

page.js

408 ms

collect

collect

367 ms

feed-icon16x16.png

feed-icon16x16.png

404 ms

shin-urayasu1000-top2.jpg

shin-urayasu1000-top2.jpg

1353 ms

bg-header.png

bg-header.png

890 ms

search-button.png

search-button.png

892 ms

isles-top.jpg

isles-top.jpg

1436 ms

sanja-top.jpg

sanja-top.jpg

1461 ms

cropped-shin-urayasu1000.jpg

cropped-shin-urayasu1000.jpg

1301 ms

IMG_2168.jpg

IMG_2168.jpg

1418 ms

IMG_8032.jpg

IMG_8032.jpg

1296 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1258 ms

dot-line.png

dot-line.png

1113 ms

icons.29.svg.js

icons.29.svg.js

37 ms

bg-section-t.png

bg-section-t.png

943 ms

bg-widget-b.png

bg-widget-b.png

1024 ms

list-style-triangle.png

list-style-triangle.png

1008 ms

dot-line-s.png

dot-line-s.png

1032 ms

translateelement.css

translateelement.css

24 ms

main.js

main.js

137 ms

fontello.woff

fontello.woff

883 ms

bg-footer.png

bg-footer.png

911 ms

bg-footer-w.png

bg-footer-w.png

943 ms

font-chocolat.woff

font-chocolat.woff

874 ms

element_main.js

element_main.js

234 ms

25b6.svg

25b6.svg

337 ms

translate_24dp.png

translate_24dp.png

33 ms

translate_24dp.png

translate_24dp.png

5 ms

l

l

25 ms

googlelogo_color_68x28dp.png

googlelogo_color_68x28dp.png

43 ms

cleardot.gif

cleardot.gif

50 ms

te_ctrl3.gif

te_ctrl3.gif

20 ms

loading.gif

loading.gif

26 ms

Accessibility Review

urayasu-fan.com accessibility score

67

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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

High

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

High

Form elements do not have associated labels

High

Links do not have a discernible 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.

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

urayasu-fan.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

urayasu-fan.com SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

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 Urayasu-fan.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 Urayasu-fan.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.

Social Sharing Optimization

urayasu-fan.com

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