Tools & Wizards About Us
weavers.space screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

weavers.space

Weaver's Space - Premium Rapidweaver Stacks and Themes for Web Designers

Page Load Speed

1.1 sec in total

First Response

158 ms

Resources Loaded

817 ms

Page Rendered

161 ms

weavers.space screenshot

About Website

Click here to check amazing Weaver S content for United States. Otherwise, check out these important facts you probably never knew about weavers.space

Weaver's Space is a marketplace for premium stacks and themes for RapidWeaver. We are a community that learn, teach, have fun and make great websites

Visit weavers.space

Key Findings

We analyzed Weavers.space page load time and found that the first response time was 158 ms and then it took 978 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

weavers.space performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.82

4/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

weavers.space

158 ms

www.weavers.space

89 ms

matomo.js

85 ms

foundation.css

41 ms

animate.min.css

55 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 85% of them (39 requests) were addressed to the original Weavers.space, 4% (2 requests) were made to Matomo.weavers.space and 2% (1 request) were made to Cloud.typography.com. The less responsive or slowest element that took the longest time to load (461 ms) relates to the external source Checkout.weavers.space.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.1 kB (9%)

Content Size

889.0 kB

After Optimization

808.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Weavers.space main page is 889.0 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. 60% of websites need less resources to load. Images take 573.9 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 80.1 kB

  • Original 94.3 kB
  • After minification 89.7 kB
  • After compression 14.2 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 80.1 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 573.9 kB
  • After minification 573.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. Weaver S images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 22 (51%)

Requests Now

43

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weavers.space

weavers.space

158 ms

www.weavers.space

www.weavers.space

89 ms

matomo.js

matomo.js

85 ms

foundation.css

foundation.css

41 ms

animate.min.css

animate.min.css

55 ms

totalcms.css

totalcms.css

62 ms

starter-grid.css

starter-grid.css

56 ms

hover-min.css

hover-min.css

58 ms

stacks_page_page0.css

stacks_page_page0.css

64 ms

global.css

global.css

77 ms

fonts.css

fonts.css

101 ms

weaversspace.svg

weaversspace.svg

76 ms

image-4830.png

image-4830.png

93 ms

image-4839.png

image-4839.png

102 ms

icon.png

icon.png

107 ms

icon.png

icon.png

106 ms

icon.png

icon.png

102 ms

icon.png

icon.png

104 ms

icon.png

icon.png

123 ms

icon.png

icon.png

143 ms

icon.png

icon.png

133 ms

image-4903.jpg

image-4903.jpg

145 ms

image-4941.jpg

image-4941.jpg

136 ms

image-4950.jpg

image-4950.jpg

135 ms

image-4959.jpg

image-4959.jpg

157 ms

image-4967.jpg

image-4967.jpg

163 ms

image-4975.jpg

image-4975.jpg

175 ms

image-4998.jpg

image-4998.jpg

183 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

177 ms

jquery.gsap3.min.js

jquery.gsap3.min.js

172 ms

totalcms.js

totalcms.js

196 ms

gsap.min.js

gsap.min.js

191 ms

jwlib-utils.js

jwlib-utils.js

207 ms

movingbox.min.js

movingbox.min.js

212 ms

vein.min.js

vein.min.js

216 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

214 ms

stacks_page_page0.js

stacks_page_page0.js

226 ms

foundation.min.js

foundation.min.js

225 ms

cart.js

cart.js

461 ms

eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOjM3NH0.LPXveMdauB3BavFnyspZBOgH_GfFDSx1fVTzLxcK-Cg

eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOjM3NH0.LPXveMdauB3BavFnyspZBOgH_GfFDSx1fVTzLxcK-Cg

85 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

99 ms

image-5004.jpg

image-5004.jpg

460 ms

matomo.php

matomo.php

125 ms

E7FDD7E6240B8E021.css

E7FDD7E6240B8E021.css

161 ms

3zPkJmgm.min.js

3zPkJmgm.min.js

57 ms

main.js

main.js

11 ms

Accessibility Review

weavers.space accessibility score

78

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-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

High

[aria-*] attributes do not have valid values

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

weavers.space 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

Missing source maps for large first-party JavaScript

SEO Factors

weavers.space SEO score

92

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

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 Weavers.space 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 Weavers.space 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

weavers.space

Open Graph data is detected on the main page of Weaver S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: