Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

blogs.qub.ac.uk

QUB Blogs – Queen's University Belfast

Page Load Speed

3.8 sec in total

First Response

1.2 sec

Resources Loaded

2.4 sec

Page Rendered

198 ms

blogs.qub.ac.uk screenshot

About Website

Welcome to blogs.qub.ac.uk homepage info - get ready to check Blogs QUB best content for United Kingdom right away, or after learning these important things about blogs.qub.ac.uk

The BlogScape for QUB Staff & Students

Visit blogs.qub.ac.uk

Key Findings

We analyzed Blogs.qub.ac.uk page load time and found that the first response time was 1.2 sec and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

blogs.qub.ac.uk performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

blogs.qub.ac.uk

1191 ms

style.css

180 ms

style2.css

793 ms

widget01.css

10 ms

cff-style.css

181 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 65% of them (17 requests) were addressed to the original Blogs.qub.ac.uk, 12% (3 requests) were made to S7.addthis.com and 8% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Blogs.qub.ac.uk.

Page Optimization Overview & Recommendations

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

Content Size

691.7 kB

After Optimization

289.3 kB

In fact, the total size of Blogs.qub.ac.uk main page is 691.7 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. Javascripts take 473.2 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 46.3 kB

  • Original 65.9 kB
  • After minification 64.9 kB
  • After compression 19.6 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 46.3 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 405 B

  • Original 90.8 kB
  • After minification 90.4 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. Blogs QUB images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 306.5 kB

  • Original 473.2 kB
  • After minification 471.8 kB
  • After compression 166.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 306.5 kB or 65% of the original size.

CSS Optimization

-80%

Potential reduce by 49.2 kB

  • Original 61.9 kB
  • After minification 52.4 kB
  • After compression 12.7 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.qub.ac.uk needs all CSS files to be minified and compressed as it can save up to 49.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (43%)

Requests Now

23

After Optimization

13

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

Accessibility Review

blogs.qub.ac.uk accessibility score

100

Accessibility Issues

Best Practices

blogs.qub.ac.uk best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

blogs.qub.ac.uk SEO score

91

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Blogs.qub.ac.uk 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.qub.ac.uk 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

Open Graph data is detected on the main page of Blogs QUB. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: