Tools & Wizards About Us
mytwitterid.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mytwitterid.com

What is my Twitter ID? A simple tool to find your Twitter ID

Page Load Speed

1.4 sec in total

First Response

216 ms

Resources Loaded

1.1 sec

Page Rendered

86 ms

mytwitterid.com screenshot

About Website

Welcome to mytwitterid.com homepage info - get ready to check My Twitter ID best content for Jordan right away, or after learning these important things about mytwitterid.com

What is my Twitter ID? You can now find your Twitter ID instantly, just enter your Twitter screen name. Search for your account ID now.

Visit mytwitterid.com

Key Findings

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

Performance Metrics

mytwitterid.com performance score

0

Network Requests Diagram

mytwitterid.com

216 ms

css

24 ms

master.min.css

66 ms

jquery.min.js

61 ms

app.min.js

157 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 19% of them (5 requests) were addressed to the original Mytwitterid.com, 19% (5 requests) were made to Pagead2.googlesyndication.com and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (309 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.0 kB (55%)

Content Size

79.9 kB

After Optimization

35.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-66%

Potential reduce by 5.4 kB

  • Original 8.1 kB
  • After minification 7.8 kB
  • After compression 2.7 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 5.4 kB or 66% of the original size.

Image Optimization

-6%

Potential reduce by 514 B

  • Original 8.9 kB
  • After minification 8.4 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. My Twitter ID images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 34.0 kB

  • Original 56.8 kB
  • After minification 56.7 kB
  • After compression 22.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 34.0 kB or 60% of the original size.

CSS Optimization

-67%

Potential reduce by 4.1 kB

  • Original 6.1 kB
  • After minification 6.1 kB
  • After compression 2.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. Mytwitterid.com needs all CSS files to be minified and compressed as it can save up to 4.1 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (42%)

Requests Now

24

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mytwitterid.com

mytwitterid.com

216 ms

css

css

24 ms

master.min.css

master.min.css

66 ms

jquery.min.js

jquery.min.js

61 ms

app.min.js

app.min.js

157 ms

adsbygoogle.js

adsbygoogle.js

21 ms

logo-inverse.svg

logo-inverse.svg

238 ms

sdk.js

sdk.js

156 ms

widgets.js

widgets.js

146 ms

analytics.js

analytics.js

26 ms

mytwitterid-logo.png

mytwitterid-logo.png

51 ms

sprite.png

sprite.png

145 ms

ca-pub-9076329452223433.js

ca-pub-9076329452223433.js

105 ms

zrt_lookup.html

zrt_lookup.html

27 ms

show_ads_impl.js

show_ads_impl.js

49 ms

collect

collect

14 ms

collect

collect

68 ms

ads

ads

200 ms

osd.js

osd.js

13 ms

109 ms

xd_arbiter.php

xd_arbiter.php

119 ms

xd_arbiter.php

xd_arbiter.php

259 ms

abg.js

abg.js

6 ms

like.php

like.php

63 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

278 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

309 ms

SEO Factors

mytwitterid.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mytwitterid.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 Mytwitterid.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

mytwitterid.com

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