6.4 sec in total
619 ms
5.4 sec
423 ms
Click here to check amazing Pier 14 content. Otherwise, check out these important facts you probably never knew about pier14.co.za
Welcome to Pier 14, a themed shopping centre in Port Elizabeth with stores offering fashion, furniture, food and plenty more.
Visit pier14.co.zaWe analyzed Pier14.co.za page load time and found that the first response time was 619 ms 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.
pier14.co.za performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value7.5 s
4/100
25%
Value14.1 s
1/100
10%
Value860 ms
33/100
30%
Value0.113
86/100
15%
Value14.5 s
9/100
10%
619 ms
851 ms
255 ms
494 ms
495 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 26% of them (32 requests) were addressed to the original Pier14.co.za, 17% (21 requests) were made to Static.xx.fbcdn.net and 11% (14 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Pier14.co.za.
Page size can be reduced by 898.9 kB (34%)
2.6 MB
1.7 MB
In fact, the total size of Pier14.co.za main page is 2.6 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 53.7 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 53.7 kB or 71% of the original size.
Potential reduce by 8.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. Pier 14 images are well optimized though.
Potential reduce by 811.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 811.2 kB or 67% of the original size.
Potential reduce by 25.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. Pier14.co.za needs all CSS files to be minified and compressed as it can save up to 25.4 kB or 81% of the original size.
Number of requests can be reduced by 59 (55%)
108
49
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pier 14. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
pier14.co.za
619 ms
www.pier14.co.za
851 ms
stylesheet.css
255 ms
fe_menu.css
494 ms
home_slider.css
495 ms
rs-minimal-white.css
519 ms
jcarousel.css
505 ms
jquery.fancybox.css
555 ms
jquery-1.7.1.min.js
860 ms
sti0ryi.js
157 ms
addthis_widget.js
8 ms
combine.php
1741 ms
www.pier14.co.za
192 ms
analytics.js
29 ms
SM-Logo.jpg
531 ms
pier14_logo.png
531 ms
menu_bg.png
261 ms
header_1_32.jpg
1034 ms
header_1_33.jpg
1264 ms
header_1_34.jpg
1591 ms
header_1_35.jpg
2040 ms
header_1_36.jpg
1802 ms
header_1_37.jpg
1379 ms
promotion_1_pier14easter.jpg
1279 ms
top_arrow.png
1533 ms
page_1_24_pier14_279.jpg
1533 ms
parallax.jpg
1879 ms
raster.png
1771 ms
feature_3_pier14_226.jpg
1772 ms
feature_2_pier14_029.jpg
1842 ms
feature_1_pier14_078.jpg
2037 ms
2044 ms
footer_bg.jpg
2052 ms
embed
342 ms
-f2pGFRSNJ03LI9_Ok56V8na7RZm4RhmmZAiBhBjf4SffH5hggMmeMJ6Mk6f5Mw.woff
29 ms
9SDxgXkAN171JraVWmX50r_yzWJUJtDGXAviERVBikIffHPhggMmeMJ6Mk6f5MS.woff
55 ms
sdk.js
167 ms
collect
14 ms
117 ms
xd_arbiter.php
145 ms
xd_arbiter.php
404 ms
js
45 ms
init_embed.js
30 ms
common.js
58 ms
map.js
59 ms
google4.png
22 ms
overlay.js
17 ms
util.js
15 ms
onion.js
13 ms
search_impl.js
110 ms
StaticMapService.GetMapImage
111 ms
stats.js
68 ms
openhand_8_8.cur
57 ms
ViewportInfoService.GetViewportInfo
222 ms
ViewportInfoService.GetViewportInfo
37 ms
transparent.png
32 ms
kh
214 ms
controls.js
175 ms
300lo.json
124 ms
left_arrow.png
1232 ms
right_arrow.png
1416 ms
mDVcm3-1Tcy5HfEN4-NnaMNrJOqLLdVzgow11ueWnEMff5QWMUMmeMJ6Mk6f5MX.woff
107 ms
UR3MXmrZwtIyj6Hhx-WTpEhPczEh1_ixvQ0j6aYdGo9ff5dWMUMmeMJ6Mk6f5gI.woff
108 ms
6SQ_zSjhhjNPQL_rK25UhOTbxR7ZiKFVJecdlPdOm16ffJObMUMmeMJ6Mk6f5MX.woff
112 ms
KK7HhM-tu24oK8R3PpmFE3tdvGcBvtVKUtLlMZij4vvffJdbMUMmeMJ6Mk6f5gI.woff
111 ms
3qiXx0AU1RZU-b6K70wvdFwzzb3FYHd7lJudPsTcWq3ffV_VMUMmeMJ6Mk6f5Mw.woff
140 ms
5b-LS2ZLscY-IyTtfYL1s6TtQXWM3zPXpsK-kqzdwf3ffJWbMUMmeMJ6Mk6f5MS.woff
140 ms
blank.jpg
1421 ms
p.gif
200 ms
sh.8e5f85691f9aaa082472a194.html
100 ms
ViewportInfoService.GetViewportInfo
103 ms
css
129 ms
entity11.png
87 ms
vt
97 ms
vt
154 ms
vt
135 ms
vt
135 ms
vt
145 ms
vt
135 ms
vt
152 ms
mapcnt6.png
54 ms
page.php
545 ms
tmapctrl.png
30 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
22 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
31 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
39 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
39 ms
AuthenticationService.Authenticate
14 ms
McLpmVM3wCm.css
260 ms
VH4VPudaxfN.css
302 ms
Czh0gDTFcBt.css
343 ms
hhn-1r1gAPt.css
420 ms
X97l7PURgJ9.css
424 ms
q68gy-v_YMF.js
457 ms
FJmpeSpHpjS.js
479 ms
0wM5s1Khldu.js
384 ms
1bNoFZUdlYZ.js
385 ms
njO1TPvGzoR.js
434 ms
1QuX41zDRrx.js
433 ms
Oagsvfb4VWi.js
497 ms
LTv6ZK-5zxz.js
580 ms
1FCa-btixu2.js
505 ms
535071_967553526631879_4558118003983478831_n.png
241 ms
safe_image.php
223 ms
10606273_724744604246107_7439266986469011105_n.png
306 ms
12715211_949044741816091_4707510045551769249_n.jpg
379 ms
12670333_949044748482757_4040653555751404948_n.jpg
413 ms
12743915_949044811816084_7093372119717414935_n.jpg
420 ms
12745526_949044818482750_5564730230535383328_n.jpg
400 ms
12745413_948483301872235_7025857124096998899_n.jpg
451 ms
12646946_948483335205565_981586080452469423_n.jpg
403 ms
12669459_948483368538895_8615274144454644444_n.jpg
451 ms
12734115_948483435205555_8196593429878150664_n.jpg
487 ms
12715778_947964735257425_6095133632311110788_n.jpg
499 ms
12728984_947964741924091_367338047284870929_n.jpg
551 ms
wL6VQj7Ab77.png
97 ms
s7jcwEQH7Sx.png
98 ms
QDwYpIaRyfG.png
97 ms
pimRBh7B6ER.png
97 ms
K00K-UgnsKu.png
97 ms
I6-MnjEovm5.js
41 ms
pQrUxxo5oQp.js
81 ms
collect
7 ms
pier14.co.za accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
pier14.co.za 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
Page has valid source maps
pier14.co.za SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pier14.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pier14.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.
pier14.co.za
Open Graph description is not detected on the main page of Pier 14. 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: