Tools & Wizards About Us
lanistone.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lanistone.jp

ハワイの大自然に育まれたパワーストーン『ラニストーン』パワーストーン天然石のブレスレットやアクセサリー

Page Load Speed

8 sec in total

First Response

532 ms

Resources Loaded

7.2 sec

Page Rendered

209 ms

lanistone.jp screenshot

About Website

Visit lanistone.jp now to see the best up-to-date Lanistone content and also check out these interesting facts you probably never knew about lanistone.jp

パワーストーンの【Lani Stone】では、天然石を使用したブレスレットなどの販売を行っています。ハワイの大自然に育まれたパワーストーン「ラニストーン」は、金運・財運・結婚運・恋愛運などにおすすめです。

Visit lanistone.jp

Key Findings

We analyzed Lanistone.jp page load time and found that the first response time was 532 ms and then it took 7.4 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

lanistone.jp performance score

0

Network Requests Diagram

lanistone.jp

532 ms

www.lanistone.jp

683 ms

m_sys_common.css

311 ms

import.css

316 ms

script.js

336 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 93% of them (75 requests) were addressed to the original Lanistone.jp, 4% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Count2.makeshop.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Lanistone.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.3 kB (30%)

Content Size

729.9 kB

After Optimization

512.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 39.6 kB

  • Original 48.0 kB
  • After minification 42.7 kB
  • After compression 8.4 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 5.3 kB, which is 11% 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 39.6 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 20.2 kB

  • Original 453.1 kB
  • After minification 432.9 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. Lanistone images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 110.5 kB

  • Original 171.2 kB
  • After minification 169.6 kB
  • After compression 60.8 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 110.5 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 47.1 kB

  • Original 57.6 kB
  • After minification 45.2 kB
  • After compression 10.6 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. Lanistone.jp needs all CSS files to be minified and compressed as it can save up to 47.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (43%)

Requests Now

79

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lanistone. 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 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lanistone.jp

lanistone.jp

532 ms

www.lanistone.jp

www.lanistone.jp

683 ms

m_sys_common.css

m_sys_common.css

311 ms

import.css

import.css

316 ms

script.js

script.js

336 ms

jquery.min.js

jquery.min.js

501 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

352 ms

jquery.bxslider.css

jquery.bxslider.css

360 ms

check_history.css

check_history.css

333 ms

pager.css

pager.css

336 ms

shopdetail.css

shopdetail.css

352 ms

ranking.css

ranking.css

368 ms

basket.css

basket.css

373 ms

security.css

security.css

513 ms

category_menu.css

category_menu.css

1677 ms

topicpath.css

topicpath.css

681 ms

catalog.css

catalog.css

706 ms

analytics.js

analytics.js

30 ms

count2.makeshop.jp

count2.makeshop.jp

517 ms

logo.gif

logo.gif

163 ms

slide1.jpg

slide1.jpg

474 ms

slide2.jpg

slide2.jpg

497 ms

slide3.jpg

slide3.jpg

495 ms

slide4.jpg

slide4.jpg

664 ms

slide5.jpg

slide5.jpg

539 ms

slide6.jpg

slide6.jpg

702 ms

l_searchTitle.png

l_searchTitle.png

810 ms

l_categoryTitle.png

l_categoryTitle.png

804 ms

maintitle2.gif

maintitle2.gif

859 ms

0270000001783.jpg

0270000001783.jpg

869 ms

iconM.gif

iconM.gif

979 ms

0270000001793.jpg

0270000001793.jpg

1008 ms

0270000001773.jpg

0270000001773.jpg

1135 ms

0270000001763.jpg

0270000001763.jpg

1137 ms

0270000001753.jpg

0270000001753.jpg

1176 ms

0270000001743.jpg

0270000001743.jpg

1220 ms

0270000001733.jpg

0270000001733.jpg

1308 ms

maintitle1.gif

maintitle1.gif

1364 ms

0270000000563.jpg

0270000000563.jpg

1468 ms

0540000000073.jpg

0540000000073.jpg

1466 ms

iconD.gif

iconD.gif

1512 ms

0540000000133.jpg

0540000000133.jpg

1569 ms

0540000000153.jpg

0540000000153.jpg

1637 ms

0540000000143.jpg

0540000000143.jpg

1697 ms

0540000000123.jpg

0540000000123.jpg

1780 ms

0540000000103.jpg

0540000000103.jpg

1794 ms

0540000000093.jpg

0540000000093.jpg

1866 ms

rankingTitle.png

rankingTitle.png

1916 ms

0270000000362.jpg

0270000000362.jpg

2113 ms

0270000000842.jpg

0270000000842.jpg

2187 ms

0270000000392.jpg

0270000000392.jpg

2275 ms

0270000001772.jpg

0270000001772.jpg

2254 ms

0270000000512.jpg

0270000000512.jpg

2431 ms

specialtitle.gif

specialtitle.gif

2297 ms

0270000000363.jpg

0270000000363.jpg

2403 ms

collect

collect

4 ms

collect

collect

62 ms

is_show_gmo_header.html

is_show_gmo_header.html

658 ms

collect

collect

2 ms

0270000000293.jpg

0270000000293.jpg

2385 ms

0270000000393.jpg

0270000000393.jpg

2121 ms

0270000000323.jpg

0270000000323.jpg

2139 ms

0270000000333.jpg

0270000000333.jpg

2159 ms

0270000000403.jpg

0270000000403.jpg

2219 ms

body_bg.png

body_bg.png

2107 ms

hNav01.png

hNav01.png

2175 ms

hNav02.png

hNav02.png

2142 ms

hNav03.png

hNav03.png

2179 ms

hNav04.png

hNav04.png

2150 ms

headBasketSwitch1.png

headBasketSwitch1.png

2217 ms

cartBtn.png

cartBtn.png

2124 ms

gNav01.png

gNav01.png

2176 ms

gNav02.png

gNav02.png

2143 ms

gNav03.png

gNav03.png

2162 ms

gNav04.png

gNav04.png

2166 ms

gNav05.png

gNav05.png

2193 ms

l_searchBtn.png

l_searchBtn.png

2100 ms

ranking.png

ranking.png

2151 ms

pagetop.png

pagetop.png

2153 ms

footerBg.png

footerBg.png

2168 ms

bx_loader.gif

bx_loader.gif

334 ms

SEO Factors

lanistone.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lanistone.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 Lanistone.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

lanistone.jp

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