5.1 sec in total
289 ms
3.8 sec
936 ms
Visit pikaplant.com now to see the best up-to-date Pikaplant content for United States and also check out these interesting facts you probably never knew about pikaplant.com
Visit pikaplant.comWe analyzed Pikaplant.com page load time and found that the first response time was 289 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
pikaplant.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value8.7 s
1/100
25%
Value22.3 s
0/100
10%
Value670 ms
44/100
30%
Value0
100/100
15%
Value15.1 s
7/100
10%
289 ms
187 ms
15 ms
174 ms
207 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 76% of them (56 requests) were addressed to the original Pikaplant.com, 5% (4 requests) were made to Google-analytics.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Pikaplant.com.
Page size can be reduced by 738.8 kB (19%)
3.9 MB
3.1 MB
In fact, the total size of Pikaplant.com main page is 3.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. 60% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 50.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 50.4 kB or 79% of the original size.
Potential reduce by 5.4 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. Pikaplant images are well optimized though.
Potential reduce by 378.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 378.6 kB or 72% of the original size.
Potential reduce by 304.4 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. Pikaplant.com needs all CSS files to be minified and compressed as it can save up to 304.4 kB or 87% of the original size.
Number of requests can be reduced by 46 (69%)
67
21
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pikaplant. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
pikaplant.com
289 ms
language-selector.css
187 ms
jquery.min.js
15 ms
page-style.css
174 ms
woocommerce-layout.css
207 ms
woocommerce.css
207 ms
css
23 ms
styles.min.css
178 ms
checkbox.min.css
178 ms
form.min.css
347 ms
css
32 ms
css
41 ms
motioncss.css
353 ms
motioncss-widgets.css
360 ms
font-awesome.css
354 ms
magnific-popup.css
357 ms
style.css
364 ms
responsive.css
517 ms
jquery.js
624 ms
jquery-migrate.min.js
525 ms
modernizr.js
529 ms
supersized.3.2.7.js
531 ms
add-to-cart.min.js
534 ms
jquery.blockUI.min.js
697 ms
woocommerce.min.js
697 ms
jquery.cookie.min.js
700 ms
cart-fragments.min.js
710 ms
jquery.easing.min.js
713 ms
jquery.isotope.js
795 ms
jquery.carousello.js
859 ms
jquery.flexslider.js
869 ms
jquery.jgrowl.js
873 ms
jquery.gmap.min.js
874 ms
jquery.magnific-popup.js
882 ms
jquery.parallax.js
974 ms
supersized.shutter.js
1034 ms
waypoints.min.js
1040 ms
imagesloaded.js
1044 ms
mediaelement-and-player.min.js
1133 ms
us.widgets.js
1052 ms
responsive.js
1145 ms
plugins.js
1039 ms
comment-reply.min.js
1042 ms
sitepress.js
1045 ms
goal.min.js
55 ms
ga.js
7 ms
LogoWebDarkGrey.png
612 ms
CoffeaJar640.jpg
1014 ms
Pikaplant_One_L.jpg
1108 ms
mailicon.svg
732 ms
phoneicon.svg
742 ms
sdk.js
269 ms
__utm.gif
19 ms
Pikaplant_Jar_Coffea_1800.jpg
1340 ms
Pikaplant_Tableau_White_1800x1200.jpg
1251 ms
Pikaplant_One_Shelf_04_Web.jpg
1485 ms
Pikaplant_One_Kalanchoe_Web.jpg
1459 ms
analytics.js
4 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
12 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
13 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
14 ms
fontawesome-webfont.woff
1402 ms
collect
14 ms
collect
66 ms
collect
65 ms
124 ms
xd_arbiter.php
209 ms
xd_arbiter.php
420 ms
admin-ajax.php
2202 ms
Pikaplant_One_Tableau_MDW15_Lensvelt_Cane_Divan_LR.jpg
1283 ms
Tableau_Automatic_Houseplant_Watering_Tray_Pikaplant_White_03_1600x900.jpg
1220 ms
Tableau_Automatic-Plant-Watering_3.jpg
1476 ms
loader.gif
1028 ms
woocommerce-smallscreen.css
90 ms
pikaplant.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pikaplant.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
pikaplant.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pikaplant.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 Pikaplant.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.
pikaplant.com
Open Graph description is not detected on the main page of Pikaplant. 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: