Tools & Wizards About Us
pianki.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

pianki.com

Pianki | Find the Perfect Luxury Gift for Any Occasion

Page Load Speed

1.7 sec in total

First Response

154 ms

Resources Loaded

1.3 sec

Page Rendered

271 ms

pianki.com screenshot

About Website

Welcome to pianki.com homepage info - get ready to check Pianki best content for United States right away, or after learning these important things about pianki.com

Find stunning luxury lifestyle goods and gifts for any occasion at Pianki. Experience the ultimate luxury from the finest brands. Shop now and personalize your gift.

Visit pianki.com

Key Findings

We analyzed Pianki.com page load time and found that the first response time was 154 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

pianki.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.253

49/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

www.pianki.com

154 ms

core.css

35 ms

bootstrap.css

82 ms

fontello.min.css

65 ms

css2

37 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 77% of them (55 requests) were addressed to the original Pianki.com, 6% (4 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (681 ms) belongs to the original domain Pianki.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 86.9 kB (16%)

Content Size

545.5 kB

After Optimization

458.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 64.1 kB

  • Original 80.5 kB
  • After minification 80.0 kB
  • After compression 16.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. 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 64.1 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 290.0 kB
  • After minification 290.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. Pianki images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 18.5 kB

  • Original 122.0 kB
  • After minification 122.0 kB
  • After compression 103.6 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 18.5 kB or 15% of the original size.

CSS Optimization

-8%

Potential reduce by 4.3 kB

  • Original 53.0 kB
  • After minification 53.0 kB
  • After compression 48.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. Pianki.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (56%)

Requests Now

62

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.pianki.com

www.pianki.com

154 ms

core.css

core.css

35 ms

bootstrap.css

bootstrap.css

82 ms

fontello.min.css

fontello.min.css

65 ms

css2

css2

37 ms

3dmegamenu.css

3dmegamenu.css

40 ms

flexslider.css

flexslider.css

39 ms

content.min.css

content.min.css

36 ms

default.css

default.css

76 ms

conversion.js

conversion.js

94 ms

animation.css

animation.css

69 ms

animate.css

animate.css

69 ms

email-decode.min.js

email-decode.min.js

42 ms

jquery.min.js

jquery.min.js

96 ms

bootstrap.js

bootstrap.js

100 ms

core.js

core.js

98 ms

scrollreveal.min.js

scrollreveal.min.js

122 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

105 ms

main.js

main.js

129 ms

3dmegamenu.js

3dmegamenu.js

131 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

124 ms

quicksearch.css

quicksearch.css

143 ms

jquery.quicksearch.js

jquery.quicksearch.js

268 ms

instantpage.min.js

instantpage.min.js

269 ms

js

js

80 ms

ionicons.min.css

ionicons.min.css

119 ms

183 ms

bat.js

bat.js

217 ms

3vsohtn8ff

3vsohtn8ff

321 ms

gtm.js

gtm.js

144 ms

Pianki_Logo.jpg

Pianki_Logo.jpg

178 ms

Home_Pens.jpg

Home_Pens.jpg

527 ms

Home_Watches.jpg

Home_Watches.jpg

211 ms

Home_Watch_Winders.jpg

Home_Watch_Winders.jpg

142 ms

Home_Leather.jpg

Home_Leather.jpg

468 ms

Home-Wallets-Leather.jpg

Home-Wallets-Leather.jpg

142 ms

Home_Umbrellas.jpg

Home_Umbrellas.jpg

212 ms

Home_Cuff_Link.jpg

Home_Cuff_Link.jpg

190 ms

Home_Globes.jpg

Home_Globes.jpg

235 ms

Home_Chess_Sets.jpg

Home_Chess_Sets.jpg

233 ms

Home_Chocolate.jpg

Home_Chocolate.jpg

236 ms

Home_STDupont_Space_Odyssey.jpg

Home_STDupont_Space_Odyssey.jpg

279 ms

Home_Look_Helios.jpg

Home_Look_Helios.jpg

289 ms

1622_481_thumbnail.jpg

1622_481_thumbnail.jpg

288 ms

un243_thumbnail.jpg

un243_thumbnail.jpg

377 ms

90003791907_thumbnail.jpg

90003791907_thumbnail.jpg

341 ms

chaos_ag_close_thumbnail.jpg

chaos_ag_close_thumbnail.jpg

371 ms

16827_thumbnail.jpg

16827_thumbnail.jpg

374 ms

ispjprsa_thumbnail.jpg

ispjprsa_thumbnail.jpg

401 ms

az018_1_thumbnail.jpg

az018_1_thumbnail.jpg

461 ms

myyellow3_thumbnail.jpg

myyellow3_thumbnail.jpg

436 ms

Home-Brand-Pineider.jpg

Home-Brand-Pineider.jpg

409 ms

Home-Brand-Caran.jpg

Home-Brand-Caran.jpg

422 ms

Home-Brand-ST-Dupont.jpg

Home-Brand-ST-Dupont.jpg

436 ms

Home-Brand-Underwood.jpg

Home-Brand-Underwood.jpg

451 ms

Home-Brand-Fedon.jpg

Home-Brand-Fedon.jpg

466 ms

Home-Brand-Solloshi.jpg

Home-Brand-Solloshi.jpg

501 ms

count.asp

count.asp

681 ms

3dvisit.asp

3dvisit.asp

548 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

186 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

198 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

207 ms

fontello.woff

fontello.woff

366 ms

MwQrbh3o1vLImiwAVvYawgcf2eVWEX-dTA.ttf

MwQrbh3o1vLImiwAVvYawgcf2eVWEX-dTA.ttf

69 ms

80 ms

4026238.js

4026238.js

23 ms

4026238

4026238

74 ms

clarity.js

clarity.js

16 ms

spacer.gif

spacer.gif

26 ms

flexslider-icon.woff

flexslider-icon.woff

40 ms

c.gif

c.gif

7 ms

Accessibility Review

pianki.com accessibility score

91

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

pianki.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pianki.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pianki.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Pianki.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

pianki.com

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