Tools & Wizards About Us
dustygedge.co.uk screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

dustygedge.co.uk

Dusty Gedge, Nature Conservation & Green Infrastructure Professional

Page Load Speed

3.1 sec in total

First Response

236 ms

Resources Loaded

2.5 sec

Page Rendered

372 ms

dustygedge.co.uk screenshot

About Website

Visit dustygedge.co.uk now to see the best up-to-date Dusty Gedge content and also check out these interesting facts you probably never knew about dustygedge.co.uk

Dusty Gedge is a green Infrastructure professional, public speaker, photographer, nature conservationist and social media influencer

Visit dustygedge.co.uk

Key Findings

We analyzed Dustygedge.co.uk page load time and found that the first response time was 236 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

dustygedge.co.uk performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.433

22/100

15%

TTI (Time to Interactive)

Value8.7 s

37/100

10%

Network Requests Diagram

dustygedge.co.uk

236 ms

dustygedge.co.uk

488 ms

cookie-law-info-public.css

1300 ms

cookie-law-info-gdpr.css

233 ms

modules-style.css

314 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 72% of them (42 requests) were addressed to the original Dustygedge.co.uk, 24% (14 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Dustygedge.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 285.8 kB (22%)

Content Size

1.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dustygedge.co.uk main page is 1.3 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. 60% of websites need less resources to load. Images take 542.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 212.2 kB

  • Original 254.9 kB
  • After minification 251.9 kB
  • After compression 42.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 212.2 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 542.6 kB
  • After minification 542.6 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. Dusty Gedge images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 58.3 kB

  • Original 423.1 kB
  • After minification 423.1 kB
  • After compression 364.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 58.3 kB or 14% of the original size.

CSS Optimization

-22%

Potential reduce by 15.3 kB

  • Original 69.4 kB
  • After minification 69.4 kB
  • After compression 54.1 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. Dustygedge.co.uk needs all CSS files to be minified and compressed as it can save up to 15.3 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (85%)

Requests Now

40

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dustygedge.co.uk

dustygedge.co.uk

236 ms

dustygedge.co.uk

dustygedge.co.uk

488 ms

cookie-law-info-public.css

cookie-law-info-public.css

1300 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

233 ms

modules-style.css

modules-style.css

314 ms

magnific-popup.min.css

magnific-popup.min.css

235 ms

frontend.css

frontend.css

240 ms

style.css

style.css

317 ms

css

css

30 ms

style.min.css

style.min.css

307 ms

jquery.min.js

jquery.min.js

396 ms

jquery-migrate.min.js

jquery-migrate.min.js

385 ms

cookie-law-info-public.js

cookie-law-info-public.js

388 ms

js

js

66 ms

et-divi-customizer-global.min.css

et-divi-customizer-global.min.css

388 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

324 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

396 ms

rs6.css

rs6.css

400 ms

rbtools.min.js

rbtools.min.js

557 ms

rs6.min.js

rs6.min.js

565 ms

magnific-popup.js

magnific-popup.js

414 ms

slick.min.js

slick.min.js

475 ms

counter-up.min.js

counter-up.min.js

477 ms

frontend.js

frontend.js

494 ms

idle-timer.min.js

idle-timer.min.js

553 ms

custom.js

custom.js

555 ms

scripts.min.js

scripts.min.js

654 ms

smoothscroll.js

smoothscroll.js

631 ms

jquery.fitvids.js

jquery.fitvids.js

634 ms

easypiechart.js

easypiechart.js

635 ms

salvattore.js

salvattore.js

643 ms

frontend-bundle.min.js

frontend-bundle.min.js

709 ms

frontend-bundle.min.js

frontend-bundle.min.js

711 ms

common.js

common.js

713 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

723 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

736 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

789 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

789 ms

DUSTY-ORIGNAL-FULL-web.jpg

DUSTY-ORIGNAL-FULL-web.jpg

323 ms

PN_zRfy9qWD8fEagAMg5.woff

PN_zRfy9qWD8fEagAMg5.woff

120 ms

PN_zRfy9qWD8fEagAMg6.ttf

PN_zRfy9qWD8fEagAMg6.ttf

183 ms

modules.ttf

modules.ttf

234 ms

monarch.ttf

monarch.ttf

181 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

88 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

89 ms

dg70.png

dg70.png

104 ms

DR9C4123c3a.jpg

DR9C4123c3a.jpg

317 ms

dusty-bw-1700.jpg

dusty-bw-1700.jpg

234 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4VrMPrc.woff

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4VrMPrc.woff

16 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4VrMPrQ.ttf

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4VrMPrQ.ttf

16 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMPrc.woff

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMPrc.woff

16 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMPrQ.ttf

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMPrQ.ttf

15 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4TbMPrc.woff

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4TbMPrc.woff

32 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4TbMPrQ.ttf

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4TbMPrQ.ttf

32 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4bbLPrc.woff

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4bbLPrc.woff

31 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4bbLPrQ.ttf

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4bbLPrQ.ttf

31 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LPrc.woff

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LPrc.woff

30 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LPrQ.ttf

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LPrQ.ttf

30 ms

Accessibility Review

dustygedge.co.uk accessibility score

90

Accessibility Issues

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

Buttons do not have an accessible name

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

Best Practices

dustygedge.co.uk best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

dustygedge.co.uk SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Dustygedge.co.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 Dustygedge.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

dustygedge.co.uk

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