32.7 sec in total
177 ms
25.6 sec
6.8 sec
Visit feedbase.net now to see the best up-to-date Feedbase content and also check out these interesting facts you probably never knew about feedbase.net
Plak is an online database of places of interest in South Africa. While Plak is targeted mainly at those interested in travel and tourism in South Africa, it also accommodates all types of South Afric...
Visit feedbase.netWe analyzed Feedbase.net page load time and found that the first response time was 177 ms and then it took 32.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
feedbase.net performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value5.6 s
17/100
25%
Value6.5 s
39/100
10%
Value380 ms
70/100
30%
Value0.219
57/100
15%
Value5.6 s
70/100
10%
177 ms
1850 ms
654 ms
655 ms
936 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Feedbase.net, 46% (44 requests) were made to Maps.google.com and 20% (19 requests) were made to Bizzorg.com. The less responsive or slowest element that took the longest time to load (11.5 sec) relates to the external source Bizzorg.com.
Page size can be reduced by 628.5 kB (57%)
1.1 MB
470.6 kB
In fact, the total size of Feedbase.net main page is 1.1 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. 60% of websites need less resources to load. Javascripts take 793.9 kB which makes up the majority of the site volume.
Potential reduce by 73.5 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 73.5 kB or 86% of the original size.
Potential reduce by 6.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. Feedbase images are well optimized though.
Potential reduce by 540.6 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 540.6 kB or 68% of the original size.
Potential reduce by 8.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. Feedbase.net needs all CSS files to be minified and compressed as it can save up to 8.1 kB or 80% of the original size.
Number of requests can be reduced by 56 (62%)
90
34
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Feedbase. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
feedbase.net
177 ms
plak.co.za
1850 ms
Global.css
654 ms
theme.css
655 ms
js
936 ms
MapStuff.js
1558 ms
AJAXStuff.js
1742 ms
ASStuff.js
1557 ms
JSCookMenu.js
1760 ms
theme.js
2249 ms
menu.js
2250 ms
common.js
225 ms
util.js
778 ms
marker.js
778 ms
geocoder.js
689 ms
ga.js
4541 ms
bg.jpg
7903 ms
HeadBG.jpg
7901 ms
Logo.png
7902 ms
leftbutton.gif
8576 ms
help.png
7652 ms
car.png
7652 ms
iw_close.gif
11514 ms
Olifants.jpg
11455 ms
like.php
9821 ms
FaceBook.png
10572 ms
Twitter.png
10328 ms
blank.gif
2547 ms
search.png
9519 ms
key.png
10625 ms
map.js
3731 ms
poly.js
3732 ms
layers.js
3730 ms
directions.js
2897 ms
overlay.js
5493 ms
stats.js
4436 ms
__utm.gif
3012 ms
onion.js
2547 ms
openhand_8_8.cur
9002 ms
infowindow.js
3156 ms
css
6306 ms
ViewportInfoService.GetViewportInfo
8002 ms
controls.js
2421 ms
AuthenticationService.Authenticate
9426 ms
AJAXService.php
5352 ms
0zf7krTbbuX.js
5848 ms
lH1ibRl5GKq.png
8107 ms
transparent.png
3125 ms
google4.png
1457 ms
mapcnt6.png
3954 ms
sv9.png
4264 ms
tmapctrl.png
3304 ms
cb_scout5.png
3613 ms
tmapctrl4.png
3613 ms
imgs8.png
3567 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
4185 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
4279 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
4783 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
4784 ms
YellowPin.png
3494 ms
GreenPin.png
3494 ms
BluePin.png
3492 ms
GrayPin.png
3494 ms
RedPin.png
3492 ms
PurplePin.png
3492 ms
PinkPin.png
5001 ms
vt
1020 ms
vt
621 ms
vt
570 ms
vt
569 ms
vt
592 ms
vt
571 ms
vt
770 ms
vt
591 ms
vt
743 ms
vt
564 ms
vt
1089 ms
vt
1144 ms
vt
1144 ms
vt
1144 ms
vt
1143 ms
vt
1143 ms
vt
1437 ms
vt
1477 ms
vt
1145 ms
vt
1099 ms
vt
1099 ms
vt
1390 ms
vt
1429 ms
vt
1430 ms
vt
1385 ms
vt
1862 ms
vt
1890 ms
vt
1889 ms
vt
1164 ms
vt
1162 ms
feedbase.net 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
feedbase.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
feedbase.net SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Feedbase.net 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 Feedbase.net 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.
feedbase.net
Open Graph description is not detected on the main page of Feedbase. 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: