Tools & Wizards About Us
curassy.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

curassy.com

Curassy｜アイコス・プルーム・グロー加熱式タバコ情報メディア

Page Load Speed

7.6 sec in total

First Response

1.9 sec

Resources Loaded

5.3 sec

Page Rendered

351 ms

curassy.com screenshot

About Website

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

今の時代はスモークフリーな時代！Curassy(キュラシー)ではアイコス・プルーム・グロー・リルハイブリッドなどの加熱式タバコや電子タバコ、VAPE・CBDをはじめとした様々な喫煙具の口コミ・評判や使い方を解説しているタバコに特化した情報メディアです。

Visit curassy.com

Key Findings

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

Performance Metrics

curassy.com performance score

0

Network Requests Diagram

curassy.com

1926 ms

style.css

1322 ms

custom.css

691 ms

jquery.js

1233 ms

jquery.selectboxes.pack.js

355 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 72% of them (49 requests) were addressed to the original Curassy.com, 7% (5 requests) were made to Pagead2.googlesyndication.com and 7% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Curassy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 386.9 kB (44%)

Content Size

886.3 kB

After Optimization

499.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 24.4 kB

  • Original 32.9 kB
  • After minification 30.5 kB
  • After compression 8.5 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 24.4 kB or 74% of the original size.

Image Optimization

-19%

Potential reduce by 96.7 kB

  • Original 501.2 kB
  • After minification 404.5 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. Obviously, Curassy needs image optimization as it can save up to 96.7 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 148.3 kB

  • Original 217.4 kB
  • After minification 195.9 kB
  • After compression 69.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 148.3 kB or 68% of the original size.

CSS Optimization

-87%

Potential reduce by 117.6 kB

  • Original 134.9 kB
  • After minification 93.7 kB
  • After compression 17.3 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. Curassy.com needs all CSS files to be minified and compressed as it can save up to 117.6 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

65

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

curassy.com

curassy.com

1926 ms

style.css

style.css

1322 ms

custom.css

custom.css

691 ms

jquery.js

jquery.js

1233 ms

jquery.selectboxes.pack.js

jquery.selectboxes.pack.js

355 ms

common.js

common.js

883 ms

statusChange.js

statusChange.js

531 ms

jsapi

jsapi

46 ms

widgets.js

widgets.js

89 ms

userTag.js

userTag.js

707 ms

clip.js

clip.js

720 ms

goods.js

goods.js

1244 ms

socialLogin.js

socialLogin.js

883 ms

pc_common.js

pc_common.js

902 ms

user.js

user.js

1050 ms

adsbygoogle.js

adsbygoogle.js

8 ms

m_api.php

m_api.php

2185 ms

analytics.js

analytics.js

22 ms

logo.gif

logo.gif

196 ms

search.png

search.png

197 ms

15_15_f.jpg

15_15_f.jpg

196 ms

category_icon05.png

category_icon05.png

197 ms

category_icon12.png

category_icon12.png

196 ms

category_icon08.png

category_icon08.png

195 ms

category_icon03.png

category_icon03.png

375 ms

180_180_f.jpg

180_180_f.jpg

367 ms

180_180_f.jpg

180_180_f.jpg

721 ms

180_180_f.jpg

180_180_f.jpg

699 ms

180_180_f.jpg

180_180_f.jpg

545 ms

180_180_f.jpg

180_180_f.jpg

360 ms

180_180_f.jpg

180_180_f.jpg

689 ms

180_180_f.jpg

180_180_f.jpg

710 ms

180_180_f.jpg

180_180_f.jpg

737 ms

180_180_f.jpg

180_180_f.jpg

1075 ms

180_180_f.jpg

180_180_f.jpg

1020 ms

180_180_f.jpg

180_180_f.jpg

1035 ms

180_180_f.jpg

180_180_f.jpg

1055 ms

180_180_f.jpg

180_180_f.jpg

1072 ms

180_180_f.jpg

180_180_f.jpg

921 ms

180_180_f.jpg

180_180_f.jpg

1284 ms

180_180_f.jpg

180_180_f.jpg

1184 ms

180_180_f.jpg

180_180_f.jpg

1373 ms

180_180_f.jpg

180_180_f.jpg

1400 ms

180_180_f.jpg

180_180_f.jpg

1600 ms

180_180_f.jpg

180_180_f.jpg

1426 ms

180_180_f.jpg

180_180_f.jpg

1513 ms

180_180_f.jpg

180_180_f.jpg

1646 ms

180_180_f.png

180_180_f.png

2388 ms

180_180_f.gif

180_180_f.gif

1573 ms

78f9d51180c23d2ed34733cc2dc47b49.jpg

78f9d51180c23d2ed34733cc2dc47b49.jpg

2162 ms

66521a652d6b943fed4a1bd69a6476d1.jpg

66521a652d6b943fed4a1bd69a6476d1.jpg

2494 ms

icomoon.woff

icomoon.woff

1886 ms

collect

collect

21 ms

ca-pub-1597007357827629.js

ca-pub-1597007357827629.js

98 ms

zrt_lookup.html

zrt_lookup.html

48 ms

show_ads_impl.js

show_ads_impl.js

47 ms

collect

collect

106 ms

fa-rss_white.png

fa-rss_white.png

1724 ms

ads

ads

234 ms

osd.js

osd.js

7 ms

m_js_controller.js

m_js_controller.js

22 ms

abg.js

abg.js

38 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

34 ms

nessie_icon_magazine_black.png

nessie_icon_magazine_black.png

25 ms

nessie_icon_magazine_white.png

nessie_icon_magazine_white.png

26 ms

s

s

14 ms

x_button_blue2.png

x_button_blue2.png

11 ms

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

7 ms

SEO Factors

curassy.com SEO score

0

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

curassy.com

Open Graph data is detected on the main page of Curassy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: