Tools & Wizards About Us
app.hornyfolks.co.za screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

app.hornyfolks.co.za

hornyfolks.co.za

Page Load Speed

4 sec in total

First Response

120 ms

Resources Loaded

3.8 sec

Page Rendered

121 ms

app.hornyfolks.co.za screenshot

About Website

Welcome to app.hornyfolks.co.za homepage info - get ready to check App Hornyfolks best content right away, or after learning these important things about app.hornyfolks.co.za

Visit app.hornyfolks.co.za

Key Findings

We analyzed App.hornyfolks.co.za page load time and found that the first response time was 120 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

app.hornyfolks.co.za performance score

0

Network Requests Diagram

120 ms

core-12AEF73C792EFAB9545C14DFCEA49412.css

2334 ms

theme-65B75FF76EE65B9BE929CA029E8F1040.css

453 ms

wld.min.js

23 ms

vendor.min.js

25 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original App.hornyfolks.co.za, 53% (9 requests) were made to S.wldcdn.net and 18% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source S.wldcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 516.0 kB (73%)

Content Size

705.4 kB

After Optimization

189.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of App.hornyfolks.co.za main page is 705.4 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. 35% of websites need less resources to load. CSS take 344.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 14.5 kB

  • Original 20.4 kB
  • After minification 19.6 kB
  • After compression 5.9 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 14.5 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 16.2 kB
  • After minification 16.2 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. App Hornyfolks images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 223.3 kB

  • Original 324.7 kB
  • After minification 306.0 kB
  • After compression 101.4 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 223.3 kB or 69% of the original size.

CSS Optimization

-81%

Potential reduce by 278.2 kB

  • Original 344.1 kB
  • After minification 343.0 kB
  • After compression 65.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. App.hornyfolks.co.za needs all CSS files to be minified and compressed as it can save up to 278.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (44%)

Requests Now

16

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

120 ms

core-12AEF73C792EFAB9545C14DFCEA49412.css

core-12AEF73C792EFAB9545C14DFCEA49412.css

2334 ms

theme-65B75FF76EE65B9BE929CA029E8F1040.css

theme-65B75FF76EE65B9BE929CA029E8F1040.css

453 ms

wld.min.js

wld.min.js

23 ms

vendor.min.js

vendor.min.js

25 ms

en_ZA.min.js

en_ZA.min.js

23 ms

wldlib.min.js

wldlib.min.js

22 ms

app.min.js

app.min.js

26 ms

hornyfolksheader2.jpg

hornyfolksheader2.jpg

311 ms

hornyfolksfooter.jpg

hornyfolksfooter.jpg

263 ms

all.js

all.js

94 ms

analytics.js

analytics.js

44 ms

ga.js

ga.js

43 ms

3261.php

3261.php

151 ms

collect

collect

27 ms

1x1.gif

1x1.gif

31 ms

tracker.php

tracker.php

52 ms

SEO Factors

app.hornyfolks.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 App.hornyfolks.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 App.hornyfolks.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

app.hornyfolks.co.za

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