Tools & Wizards About Us
weefudge.co.uk screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

weefudge.co.uk

Welcome to The Wee Fudge Company | Handmade Scottish Fudge

Page Load Speed

2.8 sec in total

First Response

567 ms

Resources Loaded

2 sec

Page Rendered

218 ms

weefudge.co.uk screenshot

About Website

Welcome to weefudge.co.uk homepage info - get ready to check Wee Fudge best content right away, or after learning these important things about weefudge.co.uk

Award winning artisan producer of fresh, delicious handmade fudge using only fine and 100% natural ingredients.

Visit weefudge.co.uk

Key Findings

We analyzed Weefudge.co.uk page load time and found that the first response time was 567 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

weefudge.co.uk performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.096

91/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

www.weefudge.co.uk

567 ms

core.css

230 ms

styles.css

156 ms

advanced-recent-posts-widget.css

156 ms

jquery.min.js

35 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 82% of them (32 requests) were addressed to the original Weefudge.co.uk, 5% (2 requests) were made to Google-analytics.com and 5% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (567 ms) belongs to the original domain Weefudge.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 155.8 kB (24%)

Content Size

639.5 kB

After Optimization

483.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 25.0 kB

  • Original 33.9 kB
  • After minification 32.2 kB
  • After compression 8.9 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 25.0 kB or 74% of the original size.

Image Optimization

-8%

Potential reduce by 35.8 kB

  • Original 432.2 kB
  • After minification 396.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. Wee Fudge images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 78.7 kB

  • Original 152.6 kB
  • After minification 126.3 kB
  • After compression 73.9 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 78.7 kB or 52% of the original size.

CSS Optimization

-78%

Potential reduce by 16.3 kB

  • Original 20.8 kB
  • After minification 17.8 kB
  • After compression 4.5 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. Weefudge.co.uk needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

36

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.weefudge.co.uk

www.weefudge.co.uk

567 ms

core.css

core.css

230 ms

styles.css

styles.css

156 ms

advanced-recent-posts-widget.css

advanced-recent-posts-widget.css

156 ms

jquery.min.js

jquery.min.js

35 ms

external-tracking.min.js

external-tracking.min.js

154 ms

modernizr-full-build.js

modernizr-full-build.js

238 ms

cycle.js

cycle.js

373 ms

easing.js

easing.js

251 ms

core.js

core.js

252 ms

jquery.form.min.js

jquery.form.min.js

96 ms

scripts.js

scripts.js

142 ms

ga.js

ga.js

18 ms

__utm.gif

__utm.gif

12 ms

WOWButton.png

WOWButton.png

195 ms

wee-fudge-co.png

wee-fudge-co.png

109 ms

social-sprite.png

social-sprite.png

108 ms

pattern.gif

pattern.gif

108 ms

border-top.png

border-top.png

106 ms

slide.png

slide.png

108 ms

welcome.jpg

welcome.jpg

150 ms

read-more.png

read-more.png

151 ms

people-make-gasgow1.jpg

people-make-gasgow1.jpg

228 ms

rsno.jpg

rsno.jpg

227 ms

seal-salt.jpg

seal-salt.jpg

302 ms

border-bottom.png

border-bottom.png

152 ms

raspberry.jpg

raspberry.jpg

225 ms

seasalt.jpg

seasalt.jpg

226 ms

lemon.jpg

lemon.jpg

228 ms

cranachan.jpg

cranachan.jpg

300 ms

scotland-fd.png

scotland-fd.png

301 ms

feastren.png

feastren.png

303 ms

sbs.png

sbs.png

303 ms

weedug.png

weedug.png

304 ms

how_cute_-webfont.woff

how_cute_-webfont.woff

356 ms

all.js

all.js

14 ms

control.png

control.png

330 ms

all.js

all.js

6 ms

WOWButton.png

WOWButton.png

430 ms

Accessibility Review

weefudge.co.uk accessibility score

70

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

weefudge.co.uk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

weefudge.co.uk SEO score

64

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Weefudge.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 Weefudge.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

weefudge.co.uk

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