Tools & Wizards About Us
blender.work screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

blender.work

Blender中国社区 – 这里有Blender的最新资讯

Page Load Speed

1.4 sec in total

First Response

675 ms

Resources Loaded

690 ms

Page Rendered

62 ms

blender.work screenshot

About Website

Click here to check amazing Blender content. Otherwise, check out these important facts you probably never knew about blender.work

Visit blender.work

Key Findings

We analyzed Blender.work page load time and found that the first response time was 675 ms and then it took 752 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

blender.work performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

blender.work

675 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Blender.work and no external sources were called. The less responsive or slowest element that took the longest time to load (675 ms) belongs to the original domain Blender.work.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.2 kB (6%)

Content Size

775.7 kB

After Optimization

725.5 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Blender.work main page is 775.7 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 769.8 kB which makes up the majority of the site volume.

HTML Optimization

-51%

Potential reduce by 541 B

  • Original 1.1 kB
  • After minification 1.1 kB
  • After compression 530 B

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 541 B or 51% of the original size.

Image Optimization

-6%

Potential reduce by 49.7 kB

  • Original 769.8 kB
  • After minification 720.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. Blender images are well optimized though.

CSS Optimization

-1%

Potential reduce by 44 B

  • Original 4.9 kB
  • After minification 4.9 kB
  • After compression 4.8 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. Blender.work has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Network Requests Diagram

blender.work

blender.work

675 ms

Accessibility Review

blender.work accessibility score

63

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

blender.work 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

SEO Factors

blender.work SEO score

55

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blender.work can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Blender.work 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

blender.work

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