Tools & Wizards About Us
whereinpe.co.za screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

whereinpe.co.za

Home - Where In Port Elizabeth

Page Load Speed

8.1 sec in total

First Response

2.3 sec

Resources Loaded

5.5 sec

Page Rendered

233 ms

whereinpe.co.za screenshot

About Website

Click here to check amazing Whereinpe content for South Africa. Otherwise, check out these important facts you probably never knew about whereinpe.co.za

Business Directory for the Nelson Mandela Bay Metropole, Port Elizabeth, Uitenhage, Jeffreys Bay, St Francis Bay, George, South Africa

Visit whereinpe.co.za

Key Findings

We analyzed Whereinpe.co.za page load time and found that the first response time was 2.3 sec and then it took 5.8 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

whereinpe.co.za performance score

0

Network Requests Diagram

whereinpe.co.za

2293 ms

style.css

490 ms

widgetkit-b7b60836.css

507 ms

finder.css

495 ms

style.css

496 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 88% of them (64 requests) were addressed to the original Whereinpe.co.za, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Whereinpe.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 506.4 kB (62%)

Content Size

811.1 kB

After Optimization

304.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whereinpe.co.za main page is 811.1 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. 45% of websites need less resources to load. Javascripts take 265.7 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 168.0 kB

  • Original 191.8 kB
  • After minification 178.3 kB
  • After compression 23.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. 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 168.0 kB or 88% of the original size.

Image Optimization

-8%

Potential reduce by 14.0 kB

  • Original 167.5 kB
  • After minification 153.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. Whereinpe images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 167.2 kB

  • Original 265.7 kB
  • After minification 263.8 kB
  • After compression 98.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 167.2 kB or 63% of the original size.

CSS Optimization

-84%

Potential reduce by 157.2 kB

  • Original 186.1 kB
  • After minification 152.3 kB
  • After compression 28.9 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. Whereinpe.co.za needs all CSS files to be minified and compressed as it can save up to 157.2 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

72

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whereinpe.co.za

whereinpe.co.za

2293 ms

style.css

style.css

490 ms

widgetkit-b7b60836.css

widgetkit-b7b60836.css

507 ms

finder.css

finder.css

495 ms

style.css

style.css

496 ms

jquery.min.js

jquery.min.js

800 ms

jquery-noconflict.js

jquery-noconflict.js

516 ms

jquery-migrate.min.js

jquery-migrate.min.js

733 ms

widgetkit-da628168.js

widgetkit-da628168.js

738 ms

base.css

base.css

740 ms

layout.css

layout.css

760 ms

menus.css

menus.css

761 ms

modules.css

modules.css

976 ms

tools.css

tools.css

982 ms

system.css

system.css

984 ms

extensions.css

extensions.css

1010 ms

custom.css

custom.css

1012 ms

noise_lightgrey.css

noise_lightgrey.css

1047 ms

droidsans.css

droidsans.css

1218 ms

trebuchet.css

trebuchet.css

1226 ms

bebas.css

bebas.css

1228 ms

big_shadow.css

big_shadow.css

1260 ms

style.css

style.css

1264 ms

responsive.css

responsive.css

1296 ms

print.css

print.css

1460 ms

droidsans.css

droidsans.css

1469 ms

bebas.css

bebas.css

1473 ms

warp.js

warp.js

1512 ms

responsive.js

responsive.js

1516 ms

accordionmenu.js

accordionmenu.js

1546 ms

dropdownmenu.js

dropdownmenu.js

1703 ms

template.js

template.js

1712 ms

search.js

search.js

1716 ms

lightbox.js

lightbox.js

949 ms

mediaelement-and-player.js

mediaelement-and-player.js

1204 ms

spotlight.js

spotlight.js

978 ms

base.css

base.css

1129 ms

layout.css

layout.css

1138 ms

menus.css

menus.css

1145 ms

modules.css

modules.css

1048 ms

tools.css

tools.css

1073 ms

system.css

system.css

1215 ms

system.css

system.css

1224 ms

system-all.css

system-all.css

1232 ms

responsive.css

responsive.css

978 ms

print.css

print.css

819 ms

noise_lightgrey_bg.jpg

noise_lightgrey_bg.jpg

258 ms

radial_gradient.svg

radial_gradient.svg

254 ms

logo7.png

logo7.png

258 ms

CATWALK%20BANNER-1a8d972ce4.jpg

CATWALK%20BANNER-1a8d972ce4.jpg

257 ms

background.png

background.png

736 ms

buttonoff.png

buttonoff.png

255 ms

img_wimpy_66d7fa88a5af1b449ae036c5fd27542a.jpg

img_wimpy_66d7fa88a5af1b449ae036c5fd27542a.jpg

732 ms

1-1163cc5f3d.jpg

1-1163cc5f3d.jpg

500 ms

10-11101f34ae.jpg

10-11101f34ae.jpg

502 ms

11-fdc1b0593d.jpg

11-fdc1b0593d.jpg

504 ms

DroidSans-webfont.woff

DroidSans-webfont.woff

751 ms

BebasNeue-webfont.woff

BebasNeue-webfont.woff

976 ms

nav.png

nav.png

697 ms

module_badges_line.png

module_badges_line.png

701 ms

contact_icons.png

contact_icons.png

918 ms

totop_scroller.png

totop_scroller.png

909 ms

menu_line_item.png

menu_line_item.png

932 ms

ga.js

ga.js

122 ms

slideset.js

slideset.js

952 ms

widgets.js

widgets.js

82 ms

plusone.js

plusone.js

43 ms

all.js

all.js

272 ms

__utm.gif

__utm.gif

15 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

39 ms

120 ms

xd_arbiter.php

xd_arbiter.php

226 ms

xd_arbiter.php

xd_arbiter.php

430 ms

SEO Factors

whereinpe.co.za SEO score

0

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 Whereinpe.co.za 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 Whereinpe.co.za 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

whereinpe.co.za

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