Tools & Wizards About Us
fabbly.com screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

fabbly.com

Page Load Speed

2.8 sec in total

First Response

318 ms

Resources Loaded

2.4 sec

Page Rendered

130 ms

fabbly.com screenshot

About Website

Visit fabbly.com now to see the best up-to-date Fabbly content for United States and also check out these interesting facts you probably never knew about fabbly.com

Feed your fabber with the latest 3D models and 3D .stl print files! Buy directly from designers or sell your 3D models on our 3D printing marketplace.

Visit fabbly.com

Key Findings

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

Performance Metrics

fabbly.com performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

fabbly.com

318 ms

www.fabbly.com

1066 ms

d1ce40d14280aedf6c1f687ed23ecf15_main.css

192 ms

2f6847d1257c6447938840c6312cfbac_sec.css

190 ms

1b7058fd0fec50a2a4b520eca271920f_search.css

201 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 Fabbly.com, 11% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fabbly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 230.2 kB (70%)

Content Size

329.5 kB

After Optimization

99.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 22.8 kB

  • Original 26.7 kB
  • After minification 16.0 kB
  • After compression 3.9 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 10.7 kB, which is 40% 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 22.8 kB or 85% of the original size.

Image Optimization

-35%

Potential reduce by 7.7 kB

  • Original 21.8 kB
  • After minification 14.1 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, Fabbly needs image optimization as it can save up to 7.7 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 98.8 kB

  • Original 157.1 kB
  • After minification 155.8 kB
  • After compression 58.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 98.8 kB or 63% of the original size.

CSS Optimization

-81%

Potential reduce by 100.9 kB

  • Original 123.9 kB
  • After minification 122.3 kB
  • After compression 23.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. Fabbly.com needs all CSS files to be minified and compressed as it can save up to 100.9 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

16

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fabbly.com

fabbly.com

318 ms

www.fabbly.com

www.fabbly.com

1066 ms

d1ce40d14280aedf6c1f687ed23ecf15_main.css

d1ce40d14280aedf6c1f687ed23ecf15_main.css

192 ms

2f6847d1257c6447938840c6312cfbac_sec.css

2f6847d1257c6447938840c6312cfbac_sec.css

190 ms

1b7058fd0fec50a2a4b520eca271920f_search.css

1b7058fd0fec50a2a4b520eca271920f_search.css

201 ms

jquery.min.js

jquery.min.js

573 ms

head.min.js

head.min.js

203 ms

bootstrap.js

bootstrap.js

203 ms

c41b99458adb66ee459a8821efa53155_sort_select.css

c41b99458adb66ee459a8821efa53155_sort_select.css

283 ms

head.css.js

head.css.js

94 ms

config

config

408 ms

analytics.js

analytics.js

16 ms

fabbly-small-logo.png

fabbly-small-logo.png

98 ms

fabbly-middlelogo.png

fabbly-middlelogo.png

96 ms

us.png

us.png

94 ms

icon-cart.png

icon-cart.png

97 ms

collect

collect

13 ms

top-btn-arrow.png

top-btn-arrow.png

139 ms

Accessibility Review

fabbly.com accessibility score

80

Accessibility Issues

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

Document doesn't have a <title> element

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

Best Practices

fabbly.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

fabbly.com SEO score

58

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

Document doesn't have a <title> element

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 Fabbly.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 Fabbly.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

fabbly.com

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