Tools & Wizards About Us
grace-web.jp screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

grace-web.jp

Grace Web | Just another WordPress site

Page Load Speed

4.1 sec in total

First Response

718 ms

Resources Loaded

2.9 sec

Page Rendered

498 ms

grace-web.jp screenshot

About Website

Click here to check amazing Grace Web content. Otherwise, check out these important facts you probably never knew about grace-web.jp

<font color="#336666">マスク、グローブ、紙コップ、石膏等の歯科材料をお値打ちに販売しております。</font>

Visit grace-web.jp

Key Findings

We analyzed Grace-web.jp page load time and found that the first response time was 718 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

grace-web.jp performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.061

97/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

grace-web.jp

718 ms

default.css

350 ms

dc.js

35 ms

GRACE_LOGO.png

221 ms

img_tel.png

544 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 39% of them (27 requests) were addressed to the original Grace-web.jp, 55% (38 requests) were made to Image1.shopserve.jp and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Image1.shopserve.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.6 kB (17%)

Content Size

944.2 kB

After Optimization

783.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Grace-web.jp main page is 944.2 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. 25% of websites need less resources to load. Images take 813.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 71.9 kB

  • Original 85.1 kB
  • After minification 68.5 kB
  • After compression 13.2 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 16.6 kB, which is 19% 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 71.9 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 64.4 kB

  • Original 813.2 kB
  • After minification 748.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. Grace Web images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 41 B

  • Original 17.8 kB
  • After minification 17.8 kB
  • After compression 17.7 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

-86%

Potential reduce by 24.2 kB

  • Original 28.0 kB
  • After minification 18.2 kB
  • After compression 3.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. Grace-web.jp needs all CSS files to be minified and compressed as it can save up to 24.2 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

59

After Optimization

54

  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grace Web. 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

grace-web.jp

grace-web.jp

718 ms

default.css

default.css

350 ms

dc.js

dc.js

35 ms

GRACE_LOGO.png

GRACE_LOGO.png

221 ms

img_tel.png

img_tel.png

544 ms

bg_img.jpg

bg_img.jpg

174 ms

bnr_eco.png

bnr_eco.png

165 ms

bnr_side01.png

bnr_side01.png

331 ms

13-1111.gif

13-1111.gif

341 ms

rss.gif

rss.gif

364 ms

spacer.gif

spacer.gif

363 ms

img_top.png

img_top.png

959 ms

img_top02.png

img_top02.png

368 ms

icon_new.gif

icon_new.gif

507 ms

icon_pickup.gif

icon_pickup.gif

577 ms

bnr_side02.png

bnr_side02.png

535 ms

bnr_side03.png

bnr_side03.png

551 ms

bnr_side04.png

bnr_side04.png

659 ms

bnr_twheel.gif

bnr_twheel.gif

673 ms

rank1.gif

rank1.gif

721 ms

rank2.gif

rank2.gif

740 ms

rank3.gif

rank3.gif

762 ms

rank4.gif

rank4.gif

831 ms

rank5.gif

rank5.gif

846 ms

rank6.gif

rank6.gif

898 ms

rank7.gif

rank7.gif

944 ms

rank8.gif

rank8.gif

940 ms

rank9.gif

rank9.gif

1035 ms

rank10.gif

rank10.gif

1040 ms

Z1.jpg

Z1.jpg

249 ms

3M_1.jpg

3M_1.jpg

209 ms

15-0007.jpg

15-0007.jpg

209 ms

puresilver1.jpg

puresilver1.jpg

226 ms

fressy_1.jpg

fressy_1.jpg

230 ms

parazetto.jpg

parazetto.jpg

261 ms

PR.jpg

PR.jpg

240 ms

30-1101.jpg

30-1101.jpg

232 ms

30-4001.jpg

30-4001.jpg

254 ms

30-0271.jpg

30-0271.jpg

256 ms

65-0911s.jpg

65-0911s.jpg

260 ms

60-1100.jpg

60-1100.jpg

267 ms

30-1041s.jpg

30-1041s.jpg

271 ms

30-1029s.jpg

30-1029s.jpg

279 ms

75-3008.jpg

75-3008.jpg

280 ms

70-1211.jpg

70-1211.jpg

283 ms

70-1313.jpg

70-1313.jpg

298 ms

80-1261.jpg

80-1261.jpg

296 ms

30-0341.jpg

30-0341.jpg

296 ms

30-0501s.jpg

30-0501s.jpg

302 ms

girobin.jpg

girobin.jpg

300 ms

40-0404.jpg

40-0404.jpg

306 ms

25-0821.jpg

25-0821.jpg

317 ms

40-0266.jpg

40-0266.jpg

319 ms

40-0120.jpg

40-0120.jpg

319 ms

45-3003s.jpg

45-3003s.jpg

327 ms

55-0905.jpg

55-0905.jpg

325 ms

inpage_linkid.js

inpage_linkid.js

33 ms

tracking.php

tracking.php

891 ms

footer.gif

footer.gif

935 ms

bnr_eco.png

bnr_eco.png

185 ms

bnr_side01.png

bnr_side01.png

52 ms

13-1111.gif

13-1111.gif

34 ms

img_top02.png

img_top02.png

1249 ms

oshirase.png

oshirase.png

1506 ms

bnr_side02.png

bnr_side02.png

698 ms

img_tel.png

img_tel.png

409 ms

bnr_side03.png

bnr_side03.png

795 ms

bnr_side04.png

bnr_side04.png

724 ms

bnr_twheel.gif

bnr_twheel.gif

1253 ms

Accessibility Review

grace-web.jp accessibility score

81

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.

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

grace-web.jp best practices score

92

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

SEO Factors

grace-web.jp SEO score

86

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

    N/A

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grace-web.jp 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 Grace-web.jp main page’s claimed encoding is euc-jp. 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

grace-web.jp

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