Tools & Wizards About Us
prognosis.unfuddle.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

prognosis.unfuddle.com

Unfuddle STACK - Software Project Management Online | GIT and SVN Hosting

Page Load Speed

2.3 sec in total

First Response

344 ms

Resources Loaded

1.8 sec

Page Rendered

128 ms

prognosis.unfuddle.com screenshot

About Website

Welcome to prognosis.unfuddle.com homepage info - get ready to check Prognosis Unfuddle best content for Singapore right away, or after learning these important things about prognosis.unfuddle.com

The project management tool for software developers with bug and issue tracking, Repository hosting, Task Boards and more! Sign up for a free trial now!

Visit prognosis.unfuddle.com

Key Findings

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

Performance Metrics

prognosis.unfuddle.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

28/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

prognosis.unfuddle.com

344 ms

account

93 ms

account

203 ms

new

264 ms

a

286 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 32% of them (9 requests) were addressed to the original Prognosis.unfuddle.com, 39% (11 requests) were made to D3idzv2a4g528y.cloudfront.net and 7% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (344 ms) belongs to the original domain Prognosis.unfuddle.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (79%)

Content Size

2.9 MB

After Optimization

607.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prognosis.unfuddle.com main page is 2.9 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. 50% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 8.7 kB

  • Original 12.3 kB
  • After minification 10.7 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 1.5 kB, which is 13% 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 8.7 kB or 71% of the original size.

Image Optimization

-8%

Potential reduce by 322 B

  • Original 4.2 kB
  • After minification 3.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. Prognosis Unfuddle images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 1.7 MB

  • Original 2.2 MB
  • After minification 1.9 MB
  • After compression 503.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 1.7 MB or 77% of the original size.

CSS Optimization

-86%

Potential reduce by 590.2 kB

  • Original 686.9 kB
  • After minification 622.8 kB
  • After compression 96.7 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. Prognosis.unfuddle.com needs all CSS files to be minified and compressed as it can save up to 590.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (52%)

Requests Now

21

After Optimization

10

  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prognosis Unfuddle. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

prognosis.unfuddle.com

prognosis.unfuddle.com

344 ms

account

account

93 ms

account

account

203 ms

new

new

264 ms

a

a

286 ms

css

css

121 ms

3rdParty.css

3rdParty.css

62 ms

ajaxUI.css

ajaxUI.css

95 ms

font-awesome.css

font-awesome.css

81 ms

3rdParty.js

3rdParty.js

125 ms

ajaxUI.js

ajaxUI.js

123 ms

print.css

print.css

16 ms

ga.js

ga.js

41 ms

ajax.24.transp.static.png

ajax.24.transp.static.png

21 ms

ajax.24.white.gif

ajax.24.white.gif

18 ms

i.js

i.js

71 ms

08cba0326a8b1f96cd306dbf7636ef7ebb0c8f5d.1.js

08cba0326a8b1f96cd306dbf7636ef7ebb0c8f5d.1.js

76 ms

__utm.gif

__utm.gif

20 ms

collect

collect

65 ms

ga-audiences

ga-audiences

36 ms

roundtrip.js

roundtrip.js

129 ms

page_external.css

page_external.css

16 ms

bootstrap3.css

bootstrap3.css

18 ms

twitter.svg

twitter.svg

31 ms

ajax.dots.gif

ajax.dots.gif

28 ms

facebook.svg

facebook.svg

27 ms

google_plus.svg

google_plus.svg

29 ms

stack-48@2x.png

stack-48@2x.png

30 ms

Accessibility Review

prognosis.unfuddle.com accessibility score

95

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

prognosis.unfuddle.com 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

SEO Factors

prognosis.unfuddle.com SEO score

82

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prognosis.unfuddle.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 Prognosis.unfuddle.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

prognosis.unfuddle.com

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