Tools & Wizards About Us

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

pfudge.com

Buy Fudge Online - Over 40 Flavors | Phenomenal Fudge

Page Load Speed

1.9 sec in total

First Response

106 ms

Resources Loaded

1.4 sec

Page Rendered

384 ms

About Website

Click here to check amazing P Fudge content. Otherwise, check out these important facts you probably never knew about pfudge.com

Buy fudge online from the Phenomenal Fudge! Over 40 fudge flavors chocolate & beyond shipped to your door!

Visit pfudge.com

Key Findings

We analyzed Pfudge.com page load time and found that the first response time was 106 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

pfudge.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value590 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.189

65/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

pfudge.com

106 ms

pfudge.com

505 ms

theme-bundle.polyfills.js

519 ms

theme-bundle.head_async.js

376 ms

webfont.js

63 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 9% of them (4 requests) were addressed to the original Pfudge.com, 51% (23 requests) were made to Cdn11.bigcommerce.com and 9% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (519 ms) relates to the external source Cdn11.bigcommerce.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.1 kB (12%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pfudge.com main page is 1.2 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. 70% of websites need less resources to load. Images take 890.9 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 141.0 kB

  • Original 159.0 kB
  • After minification 144.6 kB
  • After compression 18.0 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 141.0 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 890.9 kB
  • After minification 890.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. P Fudge images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.1 kB

  • Original 122.4 kB
  • After minification 122.4 kB
  • After compression 121.3 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.

CSS Optimization

-1%

Potential reduce by 62 B

  • Original 7.0 kB
  • After minification 7.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. Pfudge.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (44%)

Requests Now

39

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of P 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 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

pfudge.com accessibility score

88

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-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

pfudge.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pfudge.com SEO score

84

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

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 Pfudge.com 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 Pfudge.com 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 P 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: