Tools & Wizards About Us
pazebo.com screenshot

Report Summary

  • 0

    Performance

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

Page Load Speed

3 sec in total

First Response

755 ms

Resources Loaded

1.9 sec

Page Rendered

348 ms

pazebo.com screenshot

About Website

Click here to check amazing Pazebo content for Pakistan. Otherwise, check out these important facts you probably never knew about pazebo.com

Visit pazebo.com

Key Findings

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

Performance Metrics

pazebo.com performance score

0

Network Requests Diagram

www.pazebo.com

755 ms

reset-bootstrap.css

105 ms

style.css

96 ms

style.css

145 ms

yith_wcas_ajax_search.css

72 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 94% of them (67 requests) were addressed to the original Pazebo.com, 4% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (755 ms) belongs to the original domain Pazebo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 985.7 kB (59%)

Content Size

1.7 MB

After Optimization

682.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pazebo.com main page is 1.7 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. 65% of websites need less resources to load. CSS take 681.7 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 58.0 kB

  • Original 66.6 kB
  • After minification 59.5 kB
  • After compression 8.6 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 7.1 kB, which is 11% 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 58.0 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 21.5 kB

  • Original 470.1 kB
  • After minification 448.6 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. Pazebo images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 322.1 kB

  • Original 449.3 kB
  • After minification 411.8 kB
  • After compression 127.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 322.1 kB or 72% of the original size.

CSS Optimization

-86%

Potential reduce by 584.1 kB

  • Original 681.7 kB
  • After minification 573.9 kB
  • After compression 97.7 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. Pazebo.com needs all CSS files to be minified and compressed as it can save up to 584.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (69%)

Requests Now

67

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.pazebo.com

www.pazebo.com

755 ms

reset-bootstrap.css

reset-bootstrap.css

105 ms

style.css

style.css

96 ms

style.css

style.css

145 ms

yith_wcas_ajax_search.css

yith_wcas_ajax_search.css

72 ms

yit-advanced-reviews.css

yit-advanced-reviews.css

74 ms

ywot_style.css

ywot_style.css

170 ms

ywpi.css

ywpi.css

172 ms

prettyPhoto.css

prettyPhoto.css

172 ms

jquery.selectBox.css

jquery.selectBox.css

174 ms

wishlist.css

wishlist.css

175 ms

font-awesome.min.css

font-awesome.min.css

178 ms

style.css

style.css

187 ms

custom.css

custom.css

180 ms

jquery.js

jquery.js

205 ms

jquery-migrate.min.js

jquery-migrate.min.js

181 ms

ywar-attachments.js

ywar-attachments.js

183 ms

jquery.tooltipster.min.js

jquery.tooltipster.min.js

184 ms

ywot.js

ywot.js

202 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

68 ms

jquery.commonlibraries.js

jquery.commonlibraries.js

158 ms

jquery.layout.js

jquery.layout.js

158 ms

jquery.custom.js

jquery.custom.js

159 ms

add-to-cart.min.js

add-to-cart.min.js

160 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

161 ms

woocommerce.min.js

woocommerce.min.js

162 ms

jq-cookie.js

jq-cookie.js

162 ms

cart-fragments.min.js

cart-fragments.min.js

163 ms

yith-autocomplete.min.js

yith-autocomplete.min.js

165 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

165 ms

jquery.prettyPhoto.init.min.js

jquery.prettyPhoto.init.min.js

166 ms

jquery.selectBox.min.js

jquery.selectBox.min.js

166 ms

jquery.yith-wcwl.js

jquery.yith-wcwl.js

168 ms

responsive.js

responsive.js

167 ms

retina.js

retina.js

168 ms

twitter-text.js

twitter-text.js

170 ms

jquery.tipsy.js

jquery.tipsy.js

169 ms

jquery.cycle.min.js

jquery.cycle.min.js

170 ms

woocommerce_2.3.js

woocommerce_2.3.js

177 ms

woocommerce.js

woocommerce.js

179 ms

wp-embed.min.js

wp-embed.min.js

178 ms

frontend.min.js

frontend.min.js

175 ms

core.min.js

core.min.js

174 ms

widget.min.js

widget.min.js

204 ms

mouse.min.js

mouse.min.js

203 ms

slider.min.js

slider.min.js

203 ms

css

css

27 ms

jquery-ui-touch-punch.min.js

jquery-ui-touch-punch.min.js

203 ms

price-slider.min.js

price-slider.min.js

203 ms

nav-arrow-down.png

nav-arrow-down.png

418 ms

sprite.png

sprite.png

450 ms

Logo.jpg

Logo.jpg

418 ms

j30-300x300.jpg

j30-300x300.jpg

451 ms

wpspin_light.gif

wpspin_light.gif

449 ms

sale.png

sale.png

448 ms

Indian-Necklace-with-Earrings-1-300x300.jpg

Indian-Necklace-with-Earrings-1-300x300.jpg

451 ms

j32-300x300.jpg

j32-300x300.jpg

410 ms

j17-300x300.jpg

j17-300x300.jpg

408 ms

j451-300x300.jpg

j451-300x300.jpg

412 ms

black-chiffon-300x300.jpg

black-chiffon-300x300.jpg

404 ms

IMG-20151107-WA0028-300x300.jpg

IMG-20151107-WA0028-300x300.jpg

407 ms

IMG-20151107-WA0024-300x300.jpg

IMG-20151107-WA0024-300x300.jpg

405 ms

3-300x300.jpg

3-300x300.jpg

408 ms

j33-300x300.jpg

j33-300x300.jpg

407 ms

j14-300x300.jpg

j14-300x300.jpg

407 ms

Colorful-Neclace-set-300x300.jpg

Colorful-Neclace-set-300x300.jpg

402 ms

widget-links.png

widget-links.png

405 ms

wdyV6x3eKpdeUPQ7BJ5uUInF5uFdDttMLvmWuJdhhgs.ttf

wdyV6x3eKpdeUPQ7BJ5uUInF5uFdDttMLvmWuJdhhgs.ttf

48 ms

pEko-RqEtp45bE2P80AAKX06qf9KHRHwsVx7iw5MXmY.ttf

pEko-RqEtp45bE2P80AAKX06qf9KHRHwsVx7iw5MXmY.ttf

351 ms

LQ7WLTaITDg4OSRuOZCpsy3USBnSvpkopQaUR-2r7iU.ttf

LQ7WLTaITDg4OSRuOZCpsy3USBnSvpkopQaUR-2r7iU.ttf

382 ms

overlay.png

overlay.png

82 ms

Accessibility Review

pazebo.com accessibility score

45

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

pazebo.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

pazebo.com SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pazebo.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Pazebo.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

pazebo.com

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