Tools & Wizards About Us
community.wolfram.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

community.wolfram.com

Wolfram Community: Connect with other Users of Mathematica and Wolfram Technologies

Page Load Speed

3.7 sec in total

First Response

134 ms

Resources Loaded

3.3 sec

Page Rendered

271 ms

community.wolfram.com screenshot

About Website

Click here to check amazing Community Wolfram content for United States. Otherwise, check out these important facts you probably never knew about community.wolfram.com

Get answers to your questions about Mathematica, Wolfram Language, Wolfram|Alpha, Wolfram Cloud, and all other Wolfram technologies. Find discussions also by functionality and usage area. Share code &...

Visit community.wolfram.com

Key Findings

We analyzed Community.wolfram.com page load time and found that the first response time was 134 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

community.wolfram.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

community.wolfram.com

134 ms

community.wolfram.com

872 ms

2009nonHPheader.css

238 ms

main.css

135 ms

main.css

169 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 77% of them (69 requests) were addressed to the original Community.wolfram.com, 12% (11 requests) were made to Wolframcdn.com and 2% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (872 ms) belongs to the original domain Community.wolfram.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.7 kB (51%)

Content Size

510.9 kB

After Optimization

250.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Community.wolfram.com main page is 510.9 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. Javascripts take 178.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 151.4 kB

  • Original 172.6 kB
  • After minification 138.3 kB
  • After compression 21.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. This page needs HTML code to be minified as it can gain 34.3 kB, which is 20% 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 151.4 kB or 88% of the original size.

Image Optimization

-18%

Potential reduce by 15.2 kB

  • Original 82.7 kB
  • After minification 67.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. Obviously, Community Wolfram needs image optimization as it can save up to 15.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-50%

Potential reduce by 88.1 kB

  • Original 178.0 kB
  • After minification 173.6 kB
  • After compression 89.9 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 88.1 kB or 50% of the original size.

CSS Optimization

-8%

Potential reduce by 5.9 kB

  • Original 77.5 kB
  • After minification 76.5 kB
  • After compression 71.6 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. Community.wolfram.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 57 (74%)

Requests Now

77

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

community.wolfram.com

community.wolfram.com

134 ms

community.wolfram.com

community.wolfram.com

872 ms

2009nonHPheader.css

2009nonHPheader.css

238 ms

main.css

main.css

135 ms

main.css

main.css

169 ms

main.css

main.css

182 ms

main.css

main.css

191 ms

main.css

main.css

191 ms

main.css

main.css

189 ms

docs.css

docs.css

200 ms

jquery.marquee.css

jquery.marquee.css

200 ms

main.css

main.css

209 ms

main.css

main.css

238 ms

barebone.jsp

barebone.jsp

411 ms

main.css

main.css

292 ms

global.css

global.css

154 ms

gl-styles.en.css

gl-styles.en.css

228 ms

cookie-consent.js

cookie-consent.js

504 ms

walLoad.js

walLoad.js

219 ms

jquery.min.js

jquery.min.js

346 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

247 ms

hoverIntent.min.js

hoverIntent.min.js

249 ms

gl-head-scripts.en.js

gl-head-scripts.en.js

258 ms

analytics.js

analytics.js

278 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

281 ms

scopedCSS.min.js

scopedCSS.min.js

289 ms

wolfram-notebook-embedder.min.js

wolfram-notebook-embedder.min.js

139 ms

jquery-ui.css

jquery-ui.css

59 ms

jquery-ui.js

jquery-ui.js

128 ms

jquery.fancybox-1.3.4.js

jquery.fancybox-1.3.4.js

338 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

310 ms

prettify.js

prettify.js

377 ms

lang-mma.js

lang-mma.js

496 ms

MathJax.js

MathJax.js

494 ms

groupselector.js

groupselector.js

368 ms

main.js

main.js

375 ms

gl-footer-scripts.en.js

gl-footer-scripts.en.js

483 ms

main.js

main.js

485 ms

jquery.marquee.js

jquery.marquee.js

489 ms

main.js

main.js

387 ms

ga.js

ga.js

41 ms

cookie-consent.php

cookie-consent.php

346 ms

__utm.gif

__utm.gif

12 ms

wal.js

wal.js

645 ms

analytics.js

analytics.js

518 ms

TeX-AMS_HTML.js

TeX-AMS_HTML.js

335 ms

gl-logo-spikey.en.png

gl-logo-spikey.en.png

148 ms

gl-logo-wolfram.en.png

gl-logo-wolfram.en.png

151 ms

gl-logo-computation-meets-knowledge.en.png

gl-logo-computation-meets-knowledge.en.png

133 ms

gl-menu-icons.en.png

gl-menu-icons.en.png

133 ms

community-header-new.png

community-header-new.png

135 ms

search-icon.png

search-icon.png

135 ms

icon.png

icon.png

195 ms

icon.png

icon.png

195 ms

icon_ideas.png

icon_ideas.png

90 ms

rss.png

rss.png

82 ms

icon_questions.png

icon_questions.png

82 ms

icon.png

icon.png

81 ms

icon.png

icon.png

82 ms

icon.png

icon.png

420 ms

icon.png

icon.png

419 ms

user_portrait

user_portrait

418 ms

user_portrait

user_portrait

417 ms

user_portrait

user_portrait

417 ms

user_portrait

user_portrait

522 ms

user_portrait

user_portrait

570 ms

user_portrait

user_portrait

571 ms

user_portrait

user_portrait

572 ms

SourceSansPro-Regular.woff

SourceSansPro-Regular.woff

370 ms

SourceSansPro-Light.woff

SourceSansPro-Light.woff

371 ms

SourceSansPro-ExtraLight.woff

SourceSansPro-ExtraLight.woff

373 ms

SourceSansPro-SemiBold.woff

SourceSansPro-SemiBold.woff

372 ms

Museo300-Regular.otf

Museo300-Regular.otf

538 ms

SourceSansPro-LightItalic.woff

SourceSansPro-LightItalic.woff

471 ms

SourceSansPro-ExtraLightItalic.woff

SourceSansPro-ExtraLightItalic.woff

471 ms

SourceSansPro-Italic.woff

SourceSansPro-Italic.woff

467 ms

SourceSansPro-SemiBoldItalic.woff

SourceSansPro-SemiBoldItalic.woff

468 ms

open_window.png

open_window.png

473 ms

editors-choice-icon.png

editors-choice-icon.png

462 ms

input_shadow.png

input_shadow.png

504 ms

pagination-arrows.png

pagination-arrows.png

503 ms

start-discussion-new.png

start-discussion-new.png

506 ms

subheader_bg.png

subheader_bg.png

506 ms

339 ms

collect

collect

163 ms

wal.png

wal.png

163 ms

MenuArrow-15.png

MenuArrow-15.png

277 ms

Museo700-Regular.otf

Museo700-Regular.otf

326 ms

54 ms

51 ms

Accessibility Review

community.wolfram.com accessibility score

85

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

community.wolfram.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

community.wolfram.com SEO score

64

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Community.wolfram.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 Community.wolfram.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

community.wolfram.com

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