Tools & Wizards About Us
wildmagic.jp screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

wildmagic.jp

WILD MAGIC -The Rainbow Farm – | 東京・豊洲で手ぶらBBQならワイルドマジック

Page Load Speed

12.8 sec in total

First Response

915 ms

Resources Loaded

11.3 sec

Page Rendered

665 ms

wildmagic.jp screenshot

About Website

Welcome to wildmagic.jp homepage info - get ready to check WILD MAGIC best content for Japan right away, or after learning these important things about wildmagic.jp

2017年4月にリニューアルオープンを遂げた東京・豊洲 の都市型アウトドアパーク、WILD MAGIC。スタイリッシュな非日常空間の中、手ぶらでBBQがお楽しみいただけます！FAMILY / FRIENDS / COMMUNITY / LOVE / NATURE / URBAN / CULTUREというキーワードのもと、愛、家族の絆、仲間との楽しいひととき・・・日常生活で欠かすことのできない経験が...

Visit wildmagic.jp

Key Findings

We analyzed Wildmagic.jp page load time and found that the first response time was 915 ms and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster. This domain responded with an error, which can significantly jeopardize Wildmagic.jp rating and web reputation

Performance Metrics

wildmagic.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value43.6 s

0/100

10%

TBT (Total Blocking Time)

Value8,780 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.168

71/100

15%

TTI (Time to Interactive)

Value104.6 s

0/100

10%

Network Requests Diagram

wildmagic.jp

915 ms

jquery.js

337 ms

jquery.cycle.lite.js

404 ms

jquery.min.js

9 ms

ga.js

66 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 94% of them (59 requests) were addressed to the original Wildmagic.jp, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (9.2 sec) belongs to the original domain Wildmagic.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 563.0 kB (11%)

Content Size

5.4 MB

After Optimization

4.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wildmagic.jp main page is 5.4 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. 40% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 32.0 kB

  • Original 40.9 kB
  • After minification 38.9 kB
  • After compression 8.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. 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 32.0 kB or 78% of the original size.

Image Optimization

-10%

Potential reduce by 525.0 kB

  • Original 5.3 MB
  • After minification 4.7 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. WILD MAGIC images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 6.0 kB

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

Requests Breakdown

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

Requests Now

60

After Optimization

52

  • Images
  • JavaScript

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

Network Requests Diagram

wildmagic.jp

wildmagic.jp

915 ms

jquery.js

jquery.js

337 ms

jquery.cycle.lite.js

jquery.cycle.lite.js

404 ms

jquery.min.js

jquery.min.js

9 ms

ga.js

ga.js

66 ms

bg01.jpg

bg01.jpg

514 ms

main_logo.png

main_logo.png

839 ms

home_over.png

home_over.png

365 ms

about_on.png

about_on.png

364 ms

photos_on.png

photos_on.png

366 ms

access_on.png

access_on.png

396 ms

contact_on.png

contact_on.png

699 ms

the_third_park_on.png

the_third_park_on.png

703 ms

pitmasters_on.png

pitmasters_on.png

726 ms

container_on.png

container_on.png

759 ms

media_on.png

media_on.png

1062 ms

Globalnavi_specialplan_r.png

Globalnavi_specialplan_r.png

1060 ms

Globalnavi_specialplan_r.gif

Globalnavi_specialplan_r.gif

1067 ms

Globalnavi_events_r.png

Globalnavi_events_r.png

1082 ms

Globalnavi_bbq_r.png

Globalnavi_bbq_r.png

1139 ms

Globalnavi_member_r.png

Globalnavi_member_r.png

1166 ms

Globalnavi_videoclip_r.png

Globalnavi_videoclip_r.png

1395 ms

side_left_top.png

side_left_top.png

4343 ms

open.jpg

open.jpg

1765 ms

side_left_bottom.png

side_left_bottom.png

3702 ms

wm_002.jpg

wm_002.jpg

1976 ms

wm_002_002.jpg

wm_002_002.jpg

1997 ms

wm_002_003.jpg

wm_002_003.jpg

2262 ms

quates_003.png

quates_003.png

2096 ms

staff_wanted.png

staff_wanted.png

2700 ms

side_right_top.png

side_right_top.png

5034 ms

wm_004.jpg

wm_004.jpg

2778 ms

wm_004_002.jpg

wm_004_002.jpg

3171 ms

wm_004_003.jpg

wm_004_003.jpg

4029 ms

blank.jpg

blank.jpg

3133 ms

urban_outdoor.png

urban_outdoor.png

3858 ms

side_right_bottom.png

side_right_bottom.png

9224 ms

quates_001.jpg

quates_001.jpg

4493 ms

wm_001.jpg

wm_001.jpg

4616 ms

wm_001_002.jpg

wm_001_002.jpg

5139 ms

wm_001_003.jpg

wm_001_003.jpg

5294 ms

__utm.gif

__utm.gif

17 ms

collect

collect

59 ms

reservations.png

reservations.png

4506 ms

bbq.jpg

bbq.jpg

6084 ms

wm_005.jpg

wm_005.jpg

5962 ms

wm_005_002.jpg

wm_005_002.jpg

7012 ms

wm_005_003.jpg

wm_005_003.jpg

6648 ms

cafe.jpg

cafe.jpg

6227 ms

quates_004.png

quates_004.png

7078 ms

wm_003.jpg

wm_003.jpg

6747 ms

wm_003_002.jpg

wm_003_002.jpg

7004 ms

wm_003_003.jpg

wm_003_003.jpg

7340 ms

love_kingdom.jpg

love_kingdom.jpg

8983 ms

footer_logo.png

footer_logo.png

6796 ms

banner_workshopresort.png

banner_workshopresort.png

7232 ms

youtube_logo.png

youtube_logo.png

7039 ms

facebook_logo.png

facebook_logo.png

7434 ms

toyosu22.png

toyosu22.png

7317 ms

nordisk_logo.png

nordisk_logo.png

7525 ms

moet.png

moet.png

7214 ms

carlsberg.png

carlsberg.png

7240 ms

bbq_pit_boys.png

bbq_pit_boys.png

7241 ms

Accessibility Review

wildmagic.jp accessibility score

50

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

wildmagic.jp best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

wildmagic.jp SEO score

92

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

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

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 Wildmagic.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 Wildmagic.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.

Social Sharing Optimization

wildmagic.jp

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