Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

cognitor.co.uk

Cognitor - Accountants in Bromsgrove, Worcestershire, Birmingham - Cognitor Accountancy Practice

Page Load Speed

536 ms in total

First Response

170 ms

Resources Loaded

264 ms

Page Rendered

102 ms

cognitor.co.uk screenshot

About Website

Click here to check amazing Cognitor content. Otherwise, check out these important facts you probably never knew about cognitor.co.uk

Our Introductions to what we do What is important to you? Pay less tax, Grow your wealth,Achieve Financial freedom? Accounting services Cloud software Business advice Business services To be effective...

Visit cognitor.co.uk

Key Findings

We analyzed Cognitor.co.uk page load time and found that the first response time was 170 ms and then it took 366 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

cognitor.co.uk performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value0.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

cognitor.co.uk

170 ms

ubuntu-logo.png

79 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Cognitor.co.uk and no external sources were called. The less responsive or slowest element that took the longest time to load (170 ms) belongs to the original domain Cognitor.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 603.3 kB (80%)

Content Size

751.7 kB

After Optimization

148.4 kB

In fact, the total size of Cognitor.co.uk main page is 751.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 639.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 8.2 kB

  • Original 10.9 kB
  • After minification 7.9 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 3.0 kB, which is 28% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 8.2 kB or 75% of the original size.

Image Optimization

-93%

Potential reduce by 594.7 kB

  • Original 639.7 kB
  • After minification 44.9 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. Obviously, Cognitor needs image optimization as it can save up to 594.7 kB or 93% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 383 B

  • Original 101.1 kB
  • After minification 101.1 kB
  • After compression 100.7 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. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

cognitor.co.uk accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

cognitor.co.uk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

cognitor.co.uk SEO score

67

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cognitor.co.uk can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cognitor.co.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 description is not detected on the main page of Cognitor. 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: