Tools & Wizards About Us
blogs.up.ac.za screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

blogs.up.ac.za

Higher Education | University of Pretoria

Page Load Speed

8.6 sec in total

First Response

1.7 sec

Resources Loaded

6.8 sec

Page Rendered

100 ms

blogs.up.ac.za screenshot

About Website

Click here to check amazing Blogs Up content for South Africa. Otherwise, check out these important facts you probably never knew about blogs.up.ac.za

University of Pretoria is 1 of the top research institutions in Africa and their mission is to be an internationally recognised teaching & research university.

Visit blogs.up.ac.za

Key Findings

We analyzed Blogs.up.ac.za page load time and found that the first response time was 1.7 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

blogs.up.ac.za performance score

0

Network Requests Diagram

blogs.up.ac.za

1679 ms

welcome

1785 ms

style.css

837 ms

functions.js

1118 ms

rollovers.js

563 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 81% of them (13 requests) were addressed to the original Blogs.up.ac.za, 13% (2 requests) were made to Google-analytics.com and 6% (1 request) were made to Web.up.ac.za. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Blogs.up.ac.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.8 kB (58%)

Content Size

65.2 kB

After Optimization

27.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blogs.up.ac.za main page is 65.2 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. Only 10% of websites need less resources to load. Javascripts take 33.3 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 8.5 kB

  • Original 11.6 kB
  • After minification 10.9 kB
  • After compression 3.1 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 8.5 kB or 73% of the original size.

Image Optimization

-11%

Potential reduce by 94 B

  • Original 872 B
  • After minification 778 B

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. Obviously, Blogs Up needs image optimization as it can save up to 94 B or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 14.0 kB

  • Original 33.3 kB
  • After minification 23.9 kB
  • After compression 19.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 14.0 kB or 42% of the original size.

CSS Optimization

-78%

Potential reduce by 15.3 kB

  • Original 19.5 kB
  • After minification 12.9 kB
  • After compression 4.3 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. Blogs.up.ac.za needs all CSS files to be minified and compressed as it can save up to 15.3 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (38%)

Requests Now

13

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blogs.up.ac.za

blogs.up.ac.za

1679 ms

welcome

welcome

1785 ms

style.css

style.css

837 ms

functions.js

functions.js

1118 ms

rollovers.js

rollovers.js

563 ms

basic.css

basic.css

279 ms

img.css

img.css

281 ms

blog_elements.css

blog_elements.css

556 ms

forms.css

forms.css

832 ms

comments.css

comments.css

557 ms

UP_centenary_logo.jpg

UP_centenary_logo.jpg

852 ms

bg.png

bg.png

279 ms

minipost.gif

minipost.gif

278 ms

uk.gif

uk.gif

280 ms

ga.js

ga.js

9 ms

__utm.gif

__utm.gif

12 ms

SEO Factors

blogs.up.ac.za SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blogs.up.ac.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 Blogs.up.ac.za main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

blogs.up.ac.za

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