Tools & Wizards About Us

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

plumsmart.net

Sunsweet – Home of Amaz!n™ Prunes & Dried Fruits Company

Page Load Speed

4.1 sec in total

First Response

35 ms

Resources Loaded

2.1 sec

Page Rendered

1.9 sec

About Website

Visit plumsmart.net now to see the best up-to-date Plumsmart content and also check out these interesting facts you probably never knew about plumsmart.net

The magic of Sunsweet® starts at our orchards with our family of growers and reaches you through our nutritious, delicious products to enjoy year round!

Visit plumsmart.net

Key Findings

We analyzed Plumsmart.net page load time and found that the first response time was 35 ms and then it took 4 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

plumsmart.net performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.225

55/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

plumsmart.net

35 ms

www.sunsweet.com

987 ms

gtm.js

57 ms

commons.10be62a692f1ce87c08a.min.js

303 ms

global.3dedae7a60a6935cdf29.min.js

355 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Plumsmart.net, 58% (32 requests) were made to Sunsweet.com and 11% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Sunsweet.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 387.2 kB (11%)

Content Size

3.6 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Plumsmart.net main page is 3.6 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. 65% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 107.4 kB

  • Original 127.0 kB
  • After minification 102.8 kB
  • After compression 19.6 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 24.2 kB, which is 19% 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 107.4 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 43.8 kB

  • Original 3.1 MB
  • After minification 3.1 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. Plumsmart images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 136.3 kB

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

CSS Optimization

-85%

Potential reduce by 99.7 kB

  • Original 116.8 kB
  • After minification 116.5 kB
  • After compression 17.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. Plumsmart.net needs all CSS files to be minified and compressed as it can save up to 99.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (50%)

Requests Now

48

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

plumsmart.net accessibility score

100

Accessibility Issues

Best Practices

plumsmart.net best practices score

67

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

plumsmart.net 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 Plumsmart.net 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 Plumsmart.net 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 Plumsmart. 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: