5.1 sec in total
529 ms
3 sec
1.5 sec
Click here to check amazing Pink Lily content for United States. Otherwise, check out these important facts you probably never knew about pinklily.com
Ready to up your style? Visit Pink Lily for boutique fashions, trendy clothing and fab looks that are fun and affordable. Enjoy free shipping on orders over $99.
Visit pinklily.comWe analyzed Pinklily.com page load time and found that the first response time was 529 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
pinklily.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value11.2 s
0/100
25%
Value16.9 s
0/100
10%
Value5,450 ms
0/100
30%
Value0.039
100/100
15%
Value27.4 s
0/100
10%
529 ms
351 ms
400 ms
312 ms
344 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 24% of them (33 requests) were addressed to the original Pinklily.com, 30% (40 requests) were made to Cdn4.bigcommerce.com and 17% (23 requests) were made to Cdn3.bigcommerce.com. The less responsive or slowest element that took the longest time to load (687 ms) belongs to the original domain Pinklily.com.
Page size can be reduced by 859.7 kB (30%)
2.9 MB
2.0 MB
In fact, the total size of Pinklily.com main page is 2.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 95.0 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.7 kB, which is 14% 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 95.0 kB or 81% of the original size.
Potential reduce by 9.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. Pink Lily images are well optimized though.
Potential reduce by 694.5 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 694.5 kB or 69% of the original size.
Potential reduce by 60.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. Pinklily.com needs all CSS files to be minified and compressed as it can save up to 60.6 kB or 79% of the original size.
Number of requests can be reduced by 96 (76%)
126
30
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pink Lily. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
pinklily.com
529 ms
css
351 ms
base-forms.css
400 ms
styles.css
312 ms
iselector.css
344 ms
flexslider.css
334 ms
slide-show.css
344 ms
styles-slide-show.css
343 ms
social.css
333 ms
base-forms.css
333 ms
styles.css
425 ms
light.css
370 ms
theme.css
371 ms
grid.css
399 ms
responsive.css
382 ms
custom.css
383 ms
product.attributes.css
414 ms
ui.all.css
413 ms
product.quickview.css
430 ms
store.css
430 ms
imodal.css
402 ms
braintree.css
434 ms
jquery.min.js
347 ms
menudrop.js
367 ms
iselector.js
384 ms
jquery.flexslider.js
380 ms
viewport.js
368 ms
libs.js
296 ms
common.js
573 ms
init.js
575 ms
main.js
575 ms
quicksearch.js
364 ms
jquery-ui.css
573 ms
jquery-ui.min.js
429 ms
jquery.validate.js
417 ms
product.functions.js
415 ms
product.attributes.js
415 ms
quickview.js
414 ms
quickview.initialise.js
427 ms
jquery.form.js
428 ms
imodal.js
427 ms
index.js
543 ms
braintree.js
427 ms
index.js
554 ms
css
316 ms
css
315 ms
css
315 ms
css
410 ms
font-awesome.min.css
409 ms
style.css
598 ms
custom.css
687 ms
jquery.cookie.js
686 ms
bc_pinstrumentation.min.js
551 ms
jquery.bgiframe.min.js
550 ms
superfish.js
550 ms
visitor.js
550 ms
0f72429575a5fa5b0dbc8c7c6f147ca4b67ac037.js
372 ms
conversion.js
311 ms
ld.js
389 ms
css
78 ms
analytics.js
283 ms
common.js
447 ms
MYRIADPRO-REGULAR.ttf
248 ms
beacon_api.js
125 ms
analytics.min.js
122 ms
fbevents.js
524 ms
loader.png
94 ms
logo_1459885756__36717.png
170 ms
WEBSITE-Florals-new.jpg
173 ms
Website_2_1920_compressed.jpg
97 ms
Website_3_1920_compressed.jpg
172 ms
left-product-new.jpg
95 ms
middle-product-new.jpg
170 ms
right-product-new1.jpg
170 ms
tpl_icon.png
170 ms
hp-bottomcopy-section1-1-.jpg
189 ms
hp-bottomcopy-section2-1-.jpg
189 ms
app_icon.jpg
175 ms
android_icon.png
174 ms
apple_icon.png
174 ms
close.png
174 ms
signup-popup-bottom-img.jpg
284 ms
home_icon.png
291 ms
gift_cert_icon.png
284 ms
lily_logo_82_70.png
290 ms
lily_logo_22_18.png
290 ms
free_shipping.jpg
300 ms
back_by_demand.jpg
290 ms
visa_icon.png
498 ms
discover_icon.png
496 ms
paypal_icon.png
496 ms
amex_icon.png
496 ms
mastercard_icon.png
498 ms
SizingChart.jpg
497 ms
ecommerce.js
53 ms
collect
296 ms
collect
91 ms
loader0.js
258 ms
cart_bag.png
439 ms
searchIcon.png
491 ms
fornax.min.js
94 ms
MYRIADPRO-BOLD.ttf
89 ms
fontawesome-webfont.woff
90 ms
large_mountain.png
306 ms
title_under_bg_brown.png
301 ms
small_mountain.png
287 ms
recent
337 ms
ga-audiences
215 ms
mountain_newsletter.png
300 ms
clientarea_bg.jpg
453 ms
6q1c0ofG6NKsEhAc2eh-3YbN6UDyHWBl620a-IRfuBk.woff
202 ms
BVtM30trf7q_jfqYeHfjtA.woff
203 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
225 ms
1193-997-10-1021.js
62 ms
lock_icon.png
263 ms
signup_icon.jpg
292 ms
footer_heading_border.jpg
267 ms
InStockNotifyStyles.css
342 ms
134 ms
c
203 ms
14099307_1270899642920628_1711687973_n.jpg
374 ms
14099452_1672793849709252_1437013998_n.jpg
416 ms
13643579_1072099686198894_119436829_n.jpg
462 ms
14027230_1639626633019490_649234363_n.jpg
571 ms
event
246 ms
bat.js
203 ms
index.php
167 ms
arrows-ffffff.png
24 ms
16 ms
application2.js
65 ms
bg_direction_nav.png
42 ms
roundtrip.js
216 ms
dis.aspx
247 ms
storage.html
6 ms
storage.js
6 ms
pinklily.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s are not contained by their required parent element
ARIA IDs are not unique
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
pinklily.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
pinklily.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pinklily.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Pinklily.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.
pinklily.com
Open Graph description is not detected on the main page of Pink Lily. 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: