Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

williamfreese.com

William F. Reese - Painter, sculptor and artist from Wenatchee, Washington

Page Load Speed

263 ms in total

First Response

48 ms

Resources Loaded

120 ms

Page Rendered

95 ms

About Website

Visit williamfreese.com now to see the best up-to-date William F Reese content and also check out these interesting facts you probably never knew about williamfreese.com

William F. Reese is a well-known American artist and plein air painter offering original oil paintings

Visit williamfreese.com

Key Findings

We analyzed Williamfreese.com page load time and found that the first response time was 48 ms and then it took 215 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

williamfreese.com performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value0.8 s

100/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.6 s

100/100

10%

Network Requests Diagram

williamfreese.com

48 ms

bill-reese.css

12 ms

ga.js

8 ms

logo.gif

38 ms

spacer.gif

39 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 89% of them (16 requests) were addressed to the original Williamfreese.com, 11% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (48 ms) belongs to the original domain Williamfreese.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.3 kB (10%)

Content Size

96.5 kB

After Optimization

87.2 kB

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

HTML Optimization

-72%

Potential reduce by 9.0 kB

  • Original 12.5 kB
  • After minification 11.5 kB
  • After compression 3.5 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 9.0 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 111 B

  • Original 65.6 kB
  • After minification 65.5 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. William F Reese images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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. This website has mostly compressed JavaScripts.

CSS Optimization

-14%

Potential reduce by 165 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 1.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. Williamfreese.com needs all CSS files to be minified and compressed as it can save up to 165 B or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (53%)

Requests Now

17

After Optimization

8

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

Accessibility Review

williamfreese.com accessibility score

76

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.

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

Links do not have a discernible name

Best Practices

williamfreese.com best practices score

75

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

SEO Factors

williamfreese.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Williamfreese.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 Williamfreese.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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