Tools & Wizards About Us
pendo.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pendo.org

Domov

Page Load Speed

7.1 sec in total

First Response

1.6 sec

Resources Loaded

4.7 sec

Page Rendered

773 ms

pendo.org screenshot

About Website

Welcome to pendo.org homepage info - get ready to check Pendo best content right away, or after learning these important things about pendo.org

Pendo.org - Predaj čerstvého ovocia, zeleniny, ryže,múky, vajec atď.

Visit pendo.org

Key Findings

We analyzed Pendo.org page load time and found that the first response time was 1.6 sec and then it took 5.5 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

pendo.org performance score

0

Network Requests Diagram

pendo.org

1587 ms

layout.css

214 ms

jquery.fancybox.css

214 ms

jquery.fancybox-buttons.css

215 ms

jquery.fancybox-thumbs.css

216 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 49% of them (64 requests) were addressed to the original Pendo.org, 26% (34 requests) were made to Maps.google.com and 8% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Pendo.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (19%)

Content Size

7.9 MB

After Optimization

6.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pendo.org main page is 7.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. 80% 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 6.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 104.0 kB

  • Original 127.0 kB
  • After minification 122.0 kB
  • After compression 23.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. 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 104.0 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 238.0 kB

  • Original 6.1 MB
  • After minification 5.9 MB

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. Pendo images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 893.2 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 402.2 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 893.2 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 290.7 kB

  • Original 337.6 kB
  • After minification 250.5 kB
  • After compression 46.8 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. Pendo.org needs all CSS files to be minified and compressed as it can save up to 290.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (49%)

Requests Now

119

After Optimization

61

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pendo.org

pendo.org

1587 ms

layout.css

layout.css

214 ms

jquery.fancybox.css

jquery.fancybox.css

214 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

215 ms

jquery.fancybox-thumbs.css

jquery.fancybox-thumbs.css

216 ms

template.css

template.css

443 ms

all-hovers.css

all-hovers.css

217 ms

lrstyle.css

lrstyle.css

321 ms

modal.css

modal.css

321 ms

caroufredsel.css

caroufredsel.css

319 ms

camera.css

camera.css

321 ms

default_icemegamenu-reponsive.css

default_icemegamenu-reponsive.css

425 ms

style.css

style.css

431 ms

js

js

43 ms

plusone.js

plusone.js

60 ms

jquery.min.js

jquery.min.js

536 ms

jquery-noconflict.js

jquery-noconflict.js

424 ms

jquery-migrate.min.js

jquery-migrate.min.js

427 ms

caption.js

caption.js

529 ms

bootstrap.min.js

bootstrap.min.js

533 ms

mootools-core.js

mootools-core.js

645 ms

core.js

core.js

557 ms

mootools-more.js

mootools-more.js

668 ms

modal.js

modal.js

635 ms

jquery.caroufredsel.js

jquery.caroufredsel.js

749 ms

camera.min.js

camera.min.js

666 ms

tmlazyload.js

tmlazyload.js

641 ms

jsapi

jsapi

29 ms

42 ms

googleearth.js

googleearth.js

744 ms

googlemapsv3.js

googlemapsv3.js

766 ms

css

css

35 ms

plugin_googlemap3.css.php

plugin_googlemap3.css.php

774 ms

jquery.centerIn.js

jquery.centerIn.js

681 ms

jquery.modernizr.min.js

jquery.modernizr.min.js

691 ms

jquery.stellar.min.js

jquery.stellar.min.js

770 ms

jquery.simplr.smoothscroll.min.js

jquery.simplr.smoothscroll.min.js

774 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

785 ms

jquery.fancybox-buttons.js

jquery.fancybox-buttons.js

785 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

796 ms

jquery.fancybox-thumbs.js

jquery.fancybox-thumbs.js

798 ms

jquery.pep.js

jquery.pep.js

801 ms

jquery.vide.min.js

jquery.vide.min.js

799 ms

scripts.js

scripts.js

882 ms

EUCookieDirective.js

EUCookieDirective.js

793 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

default.I.js

default.I.js

3 ms

logo.png

logo.png

225 ms

all.js

all.js

268 ms

headerBg.jpg

headerBg.jpg

1276 ms

topBg.png

topBg.png

300 ms

blank.gif

blank.gif

301 ms

icon1.png

icon1.png

301 ms

icon2.png

icon2.png

460 ms

info_icon.png

info_icon.png

480 ms

camera-loader.gif

camera-loader.gif

469 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

7 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

8 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

17 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

16 ms

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

17 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

580 ms

bgIcon4.png

bgIcon4.png

424 ms

showcaseBg.jpg

showcaseBg.jpg

744 ms

bgIcon2.png

bgIcon2.png

515 ms

maintopBg.jpg

maintopBg.jpg

837 ms

template.css

template.css

714 ms

bgIcon3.png

bgIcon3.png

600 ms

footerBg.jpg

footerBg.jpg

939 ms

221 ms

xd_arbiter.php

xd_arbiter.php

323 ms

xd_arbiter.php

xd_arbiter.php

577 ms

continue_button.png

continue_button.png

565 ms

slide-1.jpg

slide-1.jpg

868 ms

common.js

common.js

35 ms

map.js

map.js

34 ms

util.js

util.js

34 ms

marker.js

marker.js

33 ms

onion.js

onion.js

27 ms

openhand_8_8.cur

openhand_8_8.cur

19 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

95 ms

stats.js

stats.js

24 ms

controls.js

controls.js

33 ms

infowindow.js

infowindow.js

18 ms

spotlight-poi.png

spotlight-poi.png

52 ms

css

css

70 ms

transparent.png

transparent.png

74 ms

google4.png

google4.png

53 ms

mapcnt6.png

mapcnt6.png

53 ms

sv5.png

sv5.png

53 ms

tmapctrl.png

tmapctrl.png

18 ms

cb_scout5.png

cb_scout5.png

20 ms

tmapctrl4.png

tmapctrl4.png

19 ms

imgs8.png

imgs8.png

55 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

37 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

37 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

38 ms

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

37 ms

vt

vt

55 ms

vt

vt

95 ms

vt

vt

42 ms

vt

vt

42 ms

vt

vt

53 ms

vt

vt

52 ms

vt

vt

59 ms

vt

vt

82 ms

vt

vt

85 ms

vt

vt

103 ms

vt

vt

102 ms

vt

vt

106 ms

vt

vt

118 ms

vt

vt

124 ms

vt

vt

121 ms

vt

vt

122 ms

vt

vt

126 ms

vt

vt

153 ms

vt

vt

143 ms

vt

vt

158 ms

vt

vt

156 ms

vt

vt

161 ms

vt

vt

169 ms

vt

vt

174 ms

vt

vt

180 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

137 ms

slide-2.jpg

slide-2.jpg

1071 ms

img1.jpg

img1.jpg

127 ms

page1-img5.jpg

page1-img5.jpg

127 ms

0r3q2gob.jpg

0r3q2gob.jpg

129 ms

page1-img3.jpg

page1-img3.jpg

129 ms

page1-img2.jpg

page1-img2.jpg

326 ms

SEO Factors

pendo.org SEO score

0

Language and Encoding

  • Language Detected

    SK

  • Language Claimed

    SK

  • Encoding

    UTF-8

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

pendo.org

Open Graph data is detected on the main page of Pendo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: