Tools & Wizards About Us
twitxr.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

twitxr.com

Page Load Speed

8.2 sec in total

First Response

498 ms

Resources Loaded

3.4 sec

Page Rendered

4.3 sec

twitxr.com screenshot

About Website

Click here to check amazing Twitxr content for India. Otherwise, check out these important facts you probably never knew about twitxr.com

Twitxr.com - Share pictures and status updates from your mobile

Visit twitxr.com

Key Findings

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

Performance Metrics

twitxr.com performance score

0

Network Requests Diagram

twitxr.com

498 ms

style_v1.0.0.6.css

306 ms

jquery-1.2.1.min.js

1333 ms

md5.js

1067 ms

urchin.js

625 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 86% of them (19 requests) were addressed to the original Twitxr.com, 9% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Cdn.widget.polarrose.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Twitxr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 67.9 kB (45%)

Content Size

150.2 kB

After Optimization

82.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Twitxr.com main page is 150.2 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 65.0 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 7.4 kB

  • Original 10.7 kB
  • After minification 10.1 kB
  • After compression 3.4 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. 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 7.4 kB or 69% of the original size.

Image Optimization

-17%

Potential reduce by 10.8 kB

  • Original 63.7 kB
  • After minification 52.8 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, Twitxr needs image optimization as it can save up to 10.8 kB or 17% 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 41.2 kB

  • Original 65.0 kB
  • After minification 61.4 kB
  • After compression 23.8 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 41.2 kB or 63% of the original size.

CSS Optimization

-78%

Potential reduce by 8.4 kB

  • Original 10.8 kB
  • After minification 8.1 kB
  • After compression 2.3 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. Twitxr.com needs all CSS files to be minified and compressed as it can save up to 8.4 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Twitxr. According to our analytics all requests are already optimized.

Network Requests Diagram

twitxr.com

twitxr.com

498 ms

style_v1.0.0.6.css

style_v1.0.0.6.css

306 ms

jquery-1.2.1.min.js

jquery-1.2.1.min.js

1333 ms

md5.js

md5.js

1067 ms

urchin.js

urchin.js

625 ms

polarrosewidget.js

polarrosewidget.js

1833 ms

logo.gif

logo.gif

1834 ms

twitter.png

twitter.png

1832 ms

facebook.gif

facebook.gif

1831 ms

m_iphone.png

m_iphone.png

1831 ms

m_WM.png

m_WM.png

1831 ms

m_java.png

m_java.png

1829 ms

m_all.png

m_all.png

1751 ms

e_facebook.png

e_facebook.png

1789 ms

e_twitter.png

e_twitter.png

1751 ms

e_flickr.png

e_flickr.png

1750 ms

e_picasa.png

e_picasa.png

1785 ms

1775 ms

appstore_badge_small.jpg

appstore_badge_small.jpg

1957 ms

techcrunch_100.gif

techcrunch_100.gif

1956 ms

ico_adv.gif

ico_adv.gif

1492 ms

__utm.gif

__utm.gif

13 ms

SEO Factors

twitxr.com SEO score

0

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

twitxr.com

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