Tools & Wizards About Us
slenderblog.co.za screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

slenderblog.co.za

Page Load Speed

7.5 sec in total

First Response

2.3 sec

Resources Loaded

4.8 sec

Page Rendered

359 ms

slenderblog.co.za screenshot

About Website

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

Visit slenderblog.co.za

Key Findings

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

slenderblog.co.za performance score

0

Network Requests Diagram

slenderblog.co.za

2289 ms

rth4jkw.js

141 ms

style.css

750 ms

style.css

493 ms

jquery.js

796 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 55% of them (24 requests) were addressed to the original Slenderblog.co.za, 16% (7 requests) were made to Use.typekit.net and 7% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Slenderblog.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 433.8 kB (36%)

Content Size

1.2 MB

After Optimization

763.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 64.6 kB

  • Original 80.3 kB
  • After minification 76.6 kB
  • After compression 15.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 64.6 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 40.0 kB

  • Original 655.5 kB
  • After minification 615.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. Slenderblog images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 154.7 kB

  • Original 258.0 kB
  • After minification 251.4 kB
  • After compression 103.3 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 154.7 kB or 60% of the original size.

CSS Optimization

-86%

Potential reduce by 174.4 kB

  • Original 203.5 kB
  • After minification 166.1 kB
  • After compression 29.0 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. Slenderblog.co.za needs all CSS files to be minified and compressed as it can save up to 174.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (49%)

Requests Now

35

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

slenderblog.co.za

slenderblog.co.za

2289 ms

rth4jkw.js

rth4jkw.js

141 ms

style.css

style.css

750 ms

style.css

style.css

493 ms

jquery.js

jquery.js

796 ms

jquery-migrate.min.js

jquery-migrate.min.js

509 ms

slenderblog.co.za

slenderblog.co.za

198 ms

bootstrap.js

bootstrap.js

264 ms

theme.js

theme.js

488 ms

jquery.json.js

jquery.json.js

518 ms

gravityforms.min.js

gravityforms.min.js

519 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

520 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

786 ms

font-awesome.css

font-awesome.css

16 ms

css

css

26 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

266 ms

widgets.js

widgets.js

123 ms

topgray.jpg

topgray.jpg

360 ms

mobimenutoggle.png

mobimenutoggle.png

360 ms

feet.png

feet.png

1942 ms

logo.png

logo.png

364 ms

logo-health.png

logo-health.png

390 ms

logo.png

logo.png

468 ms

banners-1.jpg

banners-1.jpg

496 ms

slender-blog-banner-closed.jpeg

slender-blog-banner-closed.jpeg

506 ms

fruit.png

fruit.png

1571 ms

footerlogo.png

footerlogo.png

633 ms

signin-community.png

signin-community.png

720 ms

signin-contestant.png

signin-contestant.png

741 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

69 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

70 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

70 ms

yNrK6pd_CwE_ASPs6Lg3wICaoQtKCDRQUc9tBYiuk5GffwrUgsM-eMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

yNrK6pd_CwE_ASPs6Lg3wICaoQtKCDRQUc9tBYiuk5GffwrUgsM-eMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

70 ms

y4LlnvHL28uuo_A2mzLUrQeEVThbEAPozReo-NBFxsSffFeUgsM-eMJ6Mk6g5Myfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

y4LlnvHL28uuo_A2mzLUrQeEVThbEAPozReo-NBFxsSffFeUgsM-eMJ6Mk6g5Myfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

101 ms

HB43USWhEvnIc-gW7hInSzlnFvNaRQQ7OfeJNy2enKCffFpUgsM-eMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

HB43USWhEvnIc-gW7hInSzlnFvNaRQQ7OfeJNy2enKCffFpUgsM-eMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

119 ms

HavkRATpsezPBc-UgoSobqlwoqepZkh8TDGZUTd0Z1MffFcUgsM-eMJ6Mk6g5MFfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

HavkRATpsezPBc-UgoSobqlwoqepZkh8TDGZUTd0Z1MffFcUgsM-eMJ6Mk6g5MFfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

254 ms

analytics.js

analytics.js

22 ms

sidebarv2.js

sidebarv2.js

186 ms

counter.js

counter.js

22 ms

t.php

t.php

132 ms

collect

collect

44 ms

263a.png

263a.png

60 ms

QyKno3xWMqfdn4pm9EHKdWtyjBMnMxtAGj2c-zDXl6qffFKUgsM-eMJ6Mk6g5Mofb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

QyKno3xWMqfdn4pm9EHKdWtyjBMnMxtAGj2c-zDXl6qffFKUgsM-eMJ6Mk6g5Mofb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

37 ms

p.gif

p.gif

131 ms

SEO Factors

slenderblog.co.za SEO score

0

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

slenderblog.co.za

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