Tools & Wizards About Us
whittemoredurgin.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

whittemoredurgin.com

Whittemore-Durgin Stained Glass Supplies :: Stained Glass Supplies from Whittemore-Durgin

Page Load Speed

1.3 sec in total

First Response

60 ms

Resources Loaded

986 ms

Page Rendered

223 ms

whittemoredurgin.com screenshot

About Website

Click here to check amazing Whittemore Durgin content for United States. Otherwise, check out these important facts you probably never knew about whittemoredurgin.com

Complete resource for stained glass supplies, since 1965. Buy online or at our retail store in Rockland, Mass. Everything you need to get started in stained glass: art glass, stained glass tools, book...

Visit whittemoredurgin.com

Key Findings

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

Performance Metrics

whittemoredurgin.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

whittemoredurgin.com

60 ms

whittemoredurgin.com

460 ms

subModal.css

49 ms

jquery-ui.css

72 ms

jquery-3.3.1.min.js

109 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 76% of them (28 requests) were addressed to the original Whittemoredurgin.com, 5% (2 requests) were made to Seal.godaddy.com and 5% (2 requests) were made to Verify.authorize.net. The less responsive or slowest element that took the longest time to load (460 ms) belongs to the original domain Whittemoredurgin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 686.6 kB (65%)

Content Size

1.1 MB

After Optimization

364.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whittemoredurgin.com main page is 1.1 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. 50% of websites need less resources to load. Javascripts take 631.9 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 49.0 kB

  • Original 69.7 kB
  • After minification 66.2 kB
  • After compression 20.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 49.0 kB or 70% of the original size.

Image Optimization

-24%

Potential reduce by 66.9 kB

  • Original 283.5 kB
  • After minification 216.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. Obviously, Whittemore Durgin needs image optimization as it can save up to 66.9 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-82%

Potential reduce by 517.8 kB

  • Original 631.9 kB
  • After minification 438.8 kB
  • After compression 114.1 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 517.8 kB or 82% of the original size.

CSS Optimization

-80%

Potential reduce by 52.9 kB

  • Original 65.9 kB
  • After minification 51.6 kB
  • After compression 13.0 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. Whittemoredurgin.com needs all CSS files to be minified and compressed as it can save up to 52.9 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

34

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whittemoredurgin.com

whittemoredurgin.com

60 ms

whittemoredurgin.com

whittemoredurgin.com

460 ms

subModal.css

subModal.css

49 ms

jquery-ui.css

jquery-ui.css

72 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

109 ms

jquery-ui.js

jquery-ui.js

254 ms

common.css

common.css

102 ms

site.css

site.css

78 ms

admin.css

admin.css

82 ms

site.css

site.css

87 ms

api.js

api.js

41 ms

WebResource.axd

WebResource.axd

112 ms

ScriptResource.axd

ScriptResource.axd

113 ms

ScriptResource.axd

ScriptResource.axd

217 ms

ScriptResource.axd

ScriptResource.axd

227 ms

getSeal

getSeal

385 ms

seal.js

seal.js

100 ms

widgets.js

widgets.js

49 ms

blue-seal-153-100-whittemore-glass-5022.png

blue-seal-153-100-whittemore-glass-5022.png

124 ms

badge-7-bbb-5022.png

badge-7-bbb-5022.png

123 ms

2023-logo.png

2023-logo.png

86 ms

facebook.jpg

facebook.jpg

86 ms

cart.gif

cart.gif

87 ms

WebResource.axd

WebResource.axd

45 ms

visa.gif

visa.gif

85 ms

mc.gif

mc.gif

85 ms

discover.gif

discover.gif

85 ms

amex.gif

amex.gif

86 ms

3176-1-250-250.jpg

3176-1-250-250.jpg

95 ms

4427-1-250-250.jpg

4427-1-250-250.jpg

120 ms

stained-glass-flower.gif

stained-glass-flower.gif

119 ms

irving.jpg

irving.jpg

122 ms

kathy.jpg

kathy.jpg

118 ms

kevin.jpg

kevin.jpg

121 ms

secure90x72.gif

secure90x72.gif

60 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

32 ms

siteseal_gd_3_h_l_m.gif

siteseal_gd_3_h_l_m.gif

65 ms

Accessibility Review

whittemoredurgin.com accessibility score

84

Accessibility Issues

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

Best Practices

whittemoredurgin.com best practices score

58

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

whittemoredurgin.com SEO score

69

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

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 Whittemoredurgin.com 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 Whittemoredurgin.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

whittemoredurgin.com

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