Tools & Wizards About Us
pimiso.com screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 49

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

pimiso.com

Nature Plus Me

Page Load Speed

3.6 sec in total

First Response

1.2 sec

Resources Loaded

1.8 sec

Page Rendered

651 ms

pimiso.com screenshot

About Website

Click here to check amazing Pimiso content for United States. Otherwise, check out these important facts you probably never knew about pimiso.com

Nature Plus Me

Visit pimiso.com

Key Findings

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

Performance Metrics

pimiso.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.3 s

24/100

10%

Network Requests Diagram

pimiso.com

1241 ms

bootstrap.min.css

54 ms

all.css

25 ms

css2

53 ms

widgets.js

201 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 53% of them (28 requests) were addressed to the original Pimiso.com, 8% (4 requests) were made to Google.com and 6% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Pimiso.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.9 kB (28%)

Content Size

355.0 kB

After Optimization

256.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pimiso.com main page is 355.0 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. 75% 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. Javascripts take 237.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 34.5 kB

  • Original 44.3 kB
  • After minification 31.7 kB
  • After compression 9.8 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 12.6 kB, which is 28% 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 34.5 kB or 78% of the original size.

Image Optimization

-10%

Potential reduce by 361 B

  • Original 3.7 kB
  • After minification 3.3 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. Pimiso images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 28.1 kB

  • Original 237.0 kB
  • After minification 237.0 kB
  • After compression 208.8 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 28.1 kB or 12% of the original size.

CSS Optimization

-51%

Potential reduce by 36.0 kB

  • Original 70.1 kB
  • After minification 57.5 kB
  • After compression 34.1 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. Pimiso.com needs all CSS files to be minified and compressed as it can save up to 36.0 kB or 51% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (33%)

Requests Now

51

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pimiso.com

pimiso.com

1241 ms

bootstrap.min.css

bootstrap.min.css

54 ms

all.css

all.css

25 ms

css2

css2

53 ms

widgets.js

widgets.js

201 ms

js

js

93 ms

js

js

161 ms

cse.js

cse.js

162 ms

bootstrap.min.js

bootstrap.min.js

72 ms

site.js

site.js

43 ms

embed.js

embed.js

118 ms

ads.min.js

ads.min.js

92 ms

menu--v1.png

menu--v1.png

248 ms

best-garden-hose.webp

best-garden-hose.webp

97 ms

make-compost-easily-at-home.webp

make-compost-easily-at-home.webp

83 ms

best-gardening-shoes.webp

best-gardening-shoes.webp

241 ms

monstera-yellow-leaves-causes.webp

monstera-yellow-leaves-causes.webp

91 ms

azalea-plant-care-grow-guide.webp

azalea-plant-care-grow-guide.webp

92 ms

grow-avocado-from-seed.webp

grow-avocado-from-seed.webp

81 ms

feature-image.webp

feature-image.webp

127 ms

grow-garlic.webp

grow-garlic.webp

129 ms

celosia-flower-growing-care.webp

celosia-flower-growing-care.webp

130 ms

propagating-zz-plant.webp

propagating-zz-plant.webp

216 ms

spiderplants1.webp

spiderplants1.webp

220 ms

aloevera-propogation.webp

aloevera-propogation.webp

216 ms

garlic-store.webp

garlic-store.webp

185 ms

the-basket-full-of-oranges.webp

the-basket-full-of-oranges.webp

161 ms

feature44.webp

feature44.webp

219 ms

lavander-companion22.webp

lavander-companion22.webp

325 ms

companion-plants-to-grow-with-cucumber.webp

companion-plants-to-grow-with-cucumber.webp

240 ms

peppers-companion-plants.webp

peppers-companion-plants.webp

324 ms

mosquito-repellant-plants.webp

mosquito-repellant-plants.webp

240 ms

cactus-flowers-list.webp

cactus-flowers-list.webp

241 ms

best-rated-hedge-trimmer.webp

best-rated-hedge-trimmer.webp

402 ms

facebook.svg

facebook.svg

243 ms

twitter.svg

twitter.svg

242 ms

pin.svg

pin.svg

310 ms

instagram.svg

instagram.svg

313 ms

search--v2.png

search--v2.png

241 ms

embed_v1.0.12.js

embed_v1.0.12.js

119 ms

js

js

84 ms

load-cookie.html

load-cookie.html

132 ms

rid

rid

124 ms

cse_element__en.js

cse_element__en.js

126 ms

default+en.css

default+en.css

193 ms

default.css

default.css

197 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

85 ms

embed_lib_v1.0.12.css

embed_lib_v1.0.12.css

56 ms

embed_lib_v1.0.12.js

embed_lib_v1.0.12.js

65 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSyccg.ttf

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSyccg.ttf

103 ms

settings

settings

142 ms

async-ads.js

async-ads.js

53 ms

branding.png

branding.png

45 ms

Accessibility Review

pimiso.com accessibility score

49

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pimiso.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

pimiso.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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

pimiso.com

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