Tools & Wizards About Us
uzuya.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

uzuya.net

くるくる鍋の中が回る渦巻き鍋＋蒸し器＋落し蓋＠うず丸＠

Page Load Speed

6.1 sec in total

First Response

917 ms

Resources Loaded

5 sec

Page Rendered

228 ms

uzuya.net screenshot

About Website

Visit uzuya.net now to see the best up-to-date Uzuya content and also check out these interesting facts you probably never knew about uzuya.net

くるくる鍋の中が回る【うずまき鍋】に【蒸し器】と【落し蓋】の機能をプラス！洗い易くなって・・１台３役！￥3,150-

Visit uzuya.net

Key Findings

We analyzed Uzuya.net page load time and found that the first response time was 917 ms and then it took 5.2 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

uzuya.net performance score

0

Network Requests Diagram

www.uzuya.net

917 ms

table.css

176 ms

show_ads.js

10 ms

no.css

1176 ms

no.js

1209 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 24% of them (24 requests) were addressed to the original Uzuya.net, 10% (10 requests) were made to Googleads.g.doubleclick.net and 10% (10 requests) were made to Cdn.vindicosuite.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Uzuya.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 308.3 kB (56%)

Content Size

553.9 kB

After Optimization

245.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Uzuya.net main page is 553.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. 55% of websites need less resources to load. Javascripts take 440.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 16.3 kB

  • Original 20.5 kB
  • After minification 19.7 kB
  • After compression 4.3 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 16.3 kB or 79% of the original size.

Image Optimization

-11%

Potential reduce by 9.6 kB

  • Original 90.6 kB
  • After minification 81.0 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, Uzuya needs image optimization as it can save up to 9.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 280.1 kB

  • Original 440.2 kB
  • After minification 438.3 kB
  • After compression 160.0 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 280.1 kB or 64% of the original size.

CSS Optimization

-88%

Potential reduce by 2.3 kB

  • Original 2.7 kB
  • After minification 2.1 kB
  • After compression 321 B

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. Uzuya.net needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (42%)

Requests Now

97

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.uzuya.net

www.uzuya.net

917 ms

table.css

table.css

176 ms

show_ads.js

show_ads.js

10 ms

no.css

no.css

1176 ms

no.js

no.js

1209 ms

geov2.js

geov2.js

1205 ms

n_image21.gif

n_image21.gif

319 ms

m_image21.gif

m_image21.gif

349 ms

n_image1.gif

n_image1.gif

361 ms

m_image1.gif

m_image1.gif

361 ms

n_image2.gif

n_image2.gif

376 ms

m_image2.gif

m_image2.gif

375 ms

n_image3.gif

n_image3.gif

469 ms

m_image3.gif

m_image3.gif

526 ms

n_image4.gif

n_image4.gif

586 ms

m_image4.gif

m_image4.gif

586 ms

image1.gif

image1.gif

592 ms

image2.gif

image2.gif

591 ms

P1010196.jpg

P1010196.jpg

622 ms

P1010199.jpg

P1010199.jpg

718 ms

P1010219.jpg

P1010219.jpg

781 ms

P1010220.jpg

P1010220.jpg

781 ms

P1010157.jpg

P1010157.jpg

1016 ms

a_ilst045.gif

a_ilst045.gif

782 ms

newimage2.gif

newimage2.gif

1360 ms

a_ilst046.gif

a_ilst046.gif

934 ms

object.gif

object.gif

1015 ms

image.gif

image.gif

1833 ms

ca-pub-8034596967313876.js

ca-pub-8034596967313876.js

51 ms

zrt_lookup.html

zrt_lookup.html

40 ms

show_ads_impl.js

show_ads_impl.js

78 ms

ads

ads

221 ms

osd.js

osd.js

13 ms

ads

ads

205 ms

ads

ads

255 ms

ads

ads

154 ms

ads

ads

128 ms

ads

ads

139 ms

abg.js

abg.js

31 ms

131 ms

adj

adj

136 ms

beacon

beacon

122 ms

147 ms

adj

adj

146 ms

beacon

beacon

123 ms

154 ms

adj

adj

98 ms

beacon

beacon

76 ms

17 ms

0

0

104 ms

surly.js

surly.js

211 ms

index.html

index.html

240 ms

verify_selector.js

verify_selector.js

171 ms

blank.gif

blank.gif

177 ms

20 ms

index.html

index.html

341 ms

verify_selector.js

verify_selector.js

182 ms

bapi

bapi

142 ms

blank.gif

blank.gif

180 ms

59 ms

index.html

index.html

287 ms

verify_selector.js

verify_selector.js

92 ms

blank.gif

blank.gif

96 ms

verifyr.js

verifyr.js

77 ms

ba.html

ba.html

132 ms

pixel

pixel

38 ms

pixel

pixel

153 ms

pixel

pixel

45 ms

4.gif

4.gif

159 ms

verifyr.js

verifyr.js

68 ms

lidar.js

lidar.js

45 ms

sbhK2lTE.js

sbhK2lTE.js

67 ms

verifyr.js

verifyr.js

147 ms

pixel

pixel

139 ms

beacon.js

beacon.js

224 ms

0

0

108 ms

bg.png

bg.png

108 ms

adchoices.en.png

adchoices.en.png

106 ms

dbapi

dbapi

73 ms

cTrvNaRi.html

cTrvNaRi.html

56 ms

dt

dt

229 ms

4311.js

4311.js

144 ms

setuid

setuid

187 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

15 ms

BreastAugmentation_728x90_logo.jpg

BreastAugmentation_728x90_logo.jpg

108 ms

BreastAugmentation_728x90_bg2.jpg

BreastAugmentation_728x90_bg2.jpg

107 ms

BreastAugmentation_728x90_bg1.jpg

BreastAugmentation_728x90_bg1.jpg

107 ms

dt

dt

187 ms

Rejuvenation_728x90_logo.gif

Rejuvenation_728x90_logo.gif

135 ms

Rejuvenation_728x90_bg.jpg

Rejuvenation_728x90_bg.jpg

135 ms

Rejuvenation_728x90_logo.gif

Rejuvenation_728x90_logo.gif

46 ms

MommyMakeover_728x90_bg.jpg

MommyMakeover_728x90_bg.jpg

84 ms

sd

sd

25 ms

382116061

382116061

218 ms

box_19_top-right.png

box_19_top-right.png

76 ms

ci.png

ci.png

67 ms

rapidjp-1.0.0.js

rapidjp-1.0.0.js

753 ms

lib2obf_b5.js

lib2obf_b5.js

719 ms

b

b

524 ms

SEO Factors

uzuya.net 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 Uzuya.net 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 Uzuya.net 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

uzuya.net

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