Tools & Wizards About Us
grandmarble.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

grandmarble.com

GRAND MARBLE グランマーブル　マーブルデニッシュ クルート　京都

Page Load Speed

6.7 sec in total

First Response

1.4 sec

Resources Loaded

5.1 sec

Page Rendered

264 ms

grandmarble.com screenshot

About Website

Click here to check amazing GRAND MARBLE content for Japan. Otherwise, check out these important facts you probably never knew about grandmarble.com

グランマーブルは、千年の歴史を誇るものづくりの街、京都で始まりました。京都には、異国の文化を受け入れ、それを京都らしさに昇華してきた伝統があります。

Visit grandmarble.com

Key Findings

We analyzed Grandmarble.com page load time and found that the first response time was 1.4 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

grandmarble.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value16.0 s

0/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value2.318

0/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

grandmarble.com

1356 ms

css

59 ms

css

71 ms

common.css

1788 ms

basic.css

1484 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 81% of them (42 requests) were addressed to the original Grandmarble.com, 4% (2 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Grandmarble.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 147.8 kB (6%)

Content Size

2.6 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 28.4 kB

  • Original 37.4 kB
  • After minification 35.0 kB
  • After compression 9.0 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 28.4 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 6.7 kB

  • Original 2.4 MB
  • After minification 2.4 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. GRAND MARBLE images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 43.0 kB

  • Original 79.1 kB
  • After minification 79.1 kB
  • After compression 36.1 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 43.0 kB or 54% of the original size.

CSS Optimization

-88%

Potential reduce by 69.6 kB

  • Original 79.4 kB
  • After minification 65.2 kB
  • After compression 9.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. Grandmarble.com needs all CSS files to be minified and compressed as it can save up to 69.6 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

51

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

grandmarble.com

grandmarble.com

1356 ms

css

css

59 ms

css

css

71 ms

common.css

common.css

1788 ms

basic.css

basic.css

1484 ms

index.css

index.css

1518 ms

camera.css

camera.css

1777 ms

style.css

style.css

1588 ms

jquery.min.js

jquery.min.js

6 ms

styles.css

styles.css

1345 ms

wp-embed.min.js

wp-embed.min.js

1606 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

1619 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

643 ms

sdk.js

sdk.js

17 ms

analytics.js

analytics.js

17 ms

slide_prev.png

slide_prev.png

299 ms

slide_next.png

slide_next.png

328 ms

sakura.jpg

sakura.jpg

1456 ms

gion20160319.jpg

gion20160319.jpg

1027 ms

lovemarble.jpg

lovemarble.jpg

885 ms

fondan_chocora.jpg

fondan_chocora.jpg

1484 ms

anrealage.jpg

anrealage.jpg

1279 ms

001.jpg

001.jpg

813 ms

002.jpg

002.jpg

1007 ms

003.jpg

003.jpg

1057 ms

004.jpg

004.jpg

1180 ms

bridal_selection.jpg

bridal_selection.jpg

1187 ms

birth.jpg

birth.jpg

1229 ms

recipe.jpg

recipe.jpg

1520 ms

%E7%A5%87%E5%9C%92%E4%BD%90%E5%B7%9D-kakou-80x60.jpg

%E7%A5%87%E5%9C%92%E4%BD%90%E5%B7%9D-kakou-80x60.jpg

1345 ms

%E7%9B%B8%E6%92%B22%E3%83%88%E3%83%AA%E6%B8%88%E3%81%BF-80x60.jpg

%E7%9B%B8%E6%92%B22%E3%83%88%E3%83%AA%E6%B8%88%E3%81%BF-80x60.jpg

1399 ms

official_shop.jpg

official_shop.jpg

1480 ms

blog.jpg

blog.jpg

1504 ms

gm_press_sq201601.jpg

gm_press_sq201601.jpg

1570 ms

sp_shop.jpg

sp_shop.jpg

1648 ms

noshi.jpg

noshi.jpg

1675 ms

concept.jpg

concept.jpg

1639 ms

lovemarble.jpg

lovemarble.jpg

1665 ms

parc.jpg

parc.jpg

1692 ms

radio.jpg

radio.jpg

1742 ms

sakura.jpg

sakura.jpg

1798 ms

anbox.jpg

anbox.jpg

1840 ms

banner-right_fondan_chocora02.jpg

banner-right_fondan_chocora02.jpg

1822 ms

banner-tsujiri_maccha_chocora.jpg

banner-tsujiri_maccha_chocora.jpg

1866 ms

banner-gion20160319.jpg

banner-gion20160319.jpg

2199 ms

banner-deux_lovemarble_bridal.jpg

banner-deux_lovemarble_bridal.jpg

1909 ms

0logo.png

0logo.png

1951 ms

widgets.js

widgets.js

32 ms

collect

collect

20 ms

40 ms

xd_arbiter.php

xd_arbiter.php

19 ms

xd_arbiter.php

xd_arbiter.php

28 ms

Accessibility Review

grandmarble.com accessibility score

92

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.

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

grandmarble.com 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

SEO Factors

grandmarble.com 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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grandmarble.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Grandmarble.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

grandmarble.com

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