Tools & Wizards About Us
key.digital screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

key.digital

Web Design, SEO, Social Media, Dorchester Dorset - Key Digital Agency

Page Load Speed

4 sec in total

First Response

240 ms

Resources Loaded

3.4 sec

Page Rendered

371 ms

key.digital screenshot

About Website

Click here to check amazing Key content. Otherwise, check out these important facts you probably never knew about key.digital

Digital agency in Dorchester, Dorset - content marketing, SEO strategy, website design & development, apps, social media or paid search (PPC)

Visit key.digital

Key Findings

We analyzed Key.digital page load time and found that the first response time was 240 ms and then it took 3.7 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

key.digital performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.182

67/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

Network Requests Diagram

key.digital

240 ms

key.digital

2015 ms

style.css

79 ms

custom-dashicons.css

157 ms

thickbox.css

232 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 93% of them (27 requests) were addressed to the original Key.digital, 3% (1 request) were made to Googletagmanager.com and 3% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Key.digital.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.7 kB (4%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Key.digital main page is 1.4 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 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 41.6 kB

  • Original 54.0 kB
  • After minification 50.0 kB
  • After compression 12.4 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 41.6 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 6.2 kB

  • Original 1.2 MB
  • After minification 1.2 MB

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. Key images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 8.7 kB

  • Original 70.5 kB
  • After minification 70.5 kB
  • After compression 61.8 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 8.7 kB or 12% of the original size.

CSS Optimization

-24%

Potential reduce by 2.2 kB

  • Original 9.1 kB
  • After minification 9.0 kB
  • After compression 6.9 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. Key.digital needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (23%)

Requests Now

26

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Key. 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 as a result speed up the page load time.

Network Requests Diagram

key.digital

key.digital

240 ms

key.digital

key.digital

2015 ms

style.css

style.css

79 ms

custom-dashicons.css

custom-dashicons.css

157 ms

thickbox.css

thickbox.css

232 ms

jquery.min.js

jquery.min.js

316 ms

jquery-migrate.min.js

jquery-migrate.min.js

242 ms

theme.min.js

theme.min.js

376 ms

slick.min.js

slick.min.js

240 ms

thickbox.js

thickbox.js

241 ms

gtm.js

gtm.js

112 ms

fbevents.js

fbevents.js

79 ms

Copy-of-UNLOCK2023-525x525.png

Copy-of-UNLOCK2023-525x525.png

390 ms

bullet.svg

bullet.svg

99 ms

Beverley-Holidays-logo-white-150x71.png

Beverley-Holidays-logo-white-150x71.png

101 ms

BeverleyHolidays_Sept2017-1050x440.jpg

BeverleyHolidays_Sept2017-1050x440.jpg

238 ms

Collins-Nets-Logo_Main_WHITE-150x78.png

Collins-Nets-Logo_Main_WHITE-150x78.png

98 ms

Fishing_lake-1050x440.jpeg

Fishing_lake-1050x440.jpeg

242 ms

cumulus-outdoors-logo-150x77.png

cumulus-outdoors-logo-150x77.png

171 ms

cumulus-camp-busy-1050x440.jpg

cumulus-camp-busy-1050x440.jpg

323 ms

purbeck-heaths-150x75.png

purbeck-heaths-150x75.png

172 ms

middlebere-Heath-1050x440.jpg

middlebere-Heath-1050x440.jpg

781 ms

Dorchester-Town-FC-Under-9-Raiders-team-330x330.jpg

Dorchester-Town-FC-Under-9-Raiders-team-330x330.jpg

326 ms

Portland-Port-330x330.jpeg

Portland-Port-330x330.jpeg

314 ms

Google-SGE-2-330x330.png

Google-SGE-2-330x330.png

396 ms

keydigital-red.svg

keydigital-red.svg

394 ms

dashicons.ttf

dashicons.ttf

361 ms

ajax-loader.gif

ajax-loader.gif

340 ms

key-loading.gif

key-loading.gif

398 ms

Accessibility Review

key.digital accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

key.digital 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

key.digital SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

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 Key.digital 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 Key.digital 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

key.digital

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