Tools & Wizards About Us
twitnice.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

twitnice.com

Page Load Speed

2.4 sec in total

First Response

276 ms

Resources Loaded

1.9 sec

Page Rendered

172 ms

twitnice.com screenshot

About Website

Visit twitnice.com now to see the best up-to-date Twitnice content and also check out these interesting facts you probably never knew about twitnice.com

oDesk is where the world goes to work! We are the world's largest online workplace, where savvy businesses hire, manage, and pay an on-demand workforce of talented freelancers.

Visit twitnice.com

Key Findings

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

Performance Metrics

twitnice.com performance score

0

Network Requests Diagram

twitnice.com

276 ms

jquery-2.1.0.min.js

575 ms

9352de0e7b44.css

701 ms

modernizr.custom.js

454 ms

183139605.js

320 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Twitnice.com, 38% (6 requests) were made to D1u2uhea8ugy8e.cloudfront.net and 13% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (842 ms) relates to the external source D1u2uhea8ugy8e.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 373.9 kB (49%)

Content Size

768.5 kB

After Optimization

394.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 13.0 kB

  • Original 17.5 kB
  • After minification 14.6 kB
  • After compression 4.5 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 2.9 kB, which is 17% 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 13.0 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 149.6 kB
  • After minification 149.6 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. Twitnice images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 226.4 kB

  • Original 392.8 kB
  • After minification 383.5 kB
  • After compression 166.5 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 226.4 kB or 58% of the original size.

CSS Optimization

-65%

Potential reduce by 134.6 kB

  • Original 208.6 kB
  • After minification 208.6 kB
  • After compression 74.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. Twitnice.com needs all CSS files to be minified and compressed as it can save up to 134.6 kB or 65% of the original size.

Requests Breakdown

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

Requests Now

13

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

twitnice.com

twitnice.com

276 ms

jquery-2.1.0.min.js

jquery-2.1.0.min.js

575 ms

9352de0e7b44.css

9352de0e7b44.css

701 ms

modernizr.custom.js

modernizr.custom.js

454 ms

183139605.js

183139605.js

320 ms

registration-form.js

registration-form.js

495 ms

mixpanel-2.2.min.js

mixpanel-2.2.min.js

68 ms

geo2.js

geo2.js

84 ms

dc.js

dc.js

32 ms

odesk-logo.svg

odesk-logo.svg

395 ms

hero.jpg

hero.jpg

842 ms

21 ms

gI2FFg+AAAAAVMsIOcAAA==

gI2FFg+AAAAAVMsIOcAAA==

18 ms

gI2FFg+AAAAAVMsIFUAAA==

gI2FFg+AAAAAVMsIFUAAA==

19 ms

inpage_linkid.js

inpage_linkid.js

8 ms

roundtrip.js

roundtrip.js

11 ms

SEO Factors

twitnice.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Twitnice.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Twitnice.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

twitnice.com

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