Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

weehouse.com

Alchemy Architects | Home of the weeHouse®

Page Load Speed

10.7 sec in total

First Response

3.7 sec

Resources Loaded

6.9 sec

Page Rendered

120 ms

weehouse.com screenshot

About Website

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

Alchemy Architects: Home of the weeHouse and Minnesota Architect Geoffrey Warner

Visit weehouse.com

Key Findings

We analyzed Weehouse.com page load time and found that the first response time was 3.7 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

weehouse.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value2,320 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.05

99/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

www.weehouse.com

3699 ms

wp-emoji-release.min.js

77 ms

public.css

177 ms

styles.css

189 ms

comments.css

160 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 80% of them (57 requests) were addressed to the original Weehouse.com, 3% (2 requests) were made to Assets.pinterest.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Weehouse.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 581.8 kB (29%)

Content Size

2.0 MB

After Optimization

1.4 MB

In fact, the total size of Weehouse.com main page is 2.0 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. 60% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 96.3 kB

  • Original 120.8 kB
  • After minification 119.2 kB
  • After compression 24.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. 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 96.3 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 44.6 kB

  • Original 1.3 MB
  • After minification 1.2 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. WeeHouse images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 301.0 kB

  • Original 446.1 kB
  • After minification 431.9 kB
  • After compression 145.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 301.0 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 139.9 kB

  • Original 163.1 kB
  • After minification 121.3 kB
  • After compression 23.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. Weehouse.com needs all CSS files to be minified and compressed as it can save up to 139.9 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

68

After Optimization

32

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

Accessibility Review

weehouse.com accessibility score

97

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.

Best Practices

weehouse.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

weehouse.com SEO score

92

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

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 Weehouse.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 Weehouse.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 WeeHouse. 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: