1.6 sec in total
76 ms
1.2 sec
313 ms
Welcome to twitter.dev homepage info - get ready to check Twitter best content right away, or after learning these important things about twitter.dev
Publish & analyze Tweets, optimize ads, & create unique customer experiences with the Twitter API, Twitter Ads API, & Twitter Embeds.
Visit twitter.devWe analyzed Twitter.dev page load time and found that the first response time was 76 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
twitter.dev performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value21.3 s
0/100
25%
Value10.9 s
6/100
10%
Value820 ms
35/100
30%
Value0
100/100
15%
Value16.0 s
6/100
10%
76 ms
43 ms
40 ms
50 ms
58 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Twitter.dev, 31% (12 requests) were made to Cdn.cms-twdigitalassets.com and 5% (2 requests) were made to Developer.twitter.com. The less responsive or slowest element that took the longest time to load (512 ms) relates to the external source Fonts.twitter.com.
Page size can be reduced by 123.4 kB (64%)
193.0 kB
69.6 kB
In fact, the total size of Twitter.dev main page is 193.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 138.8 kB which makes up the majority of the site volume.
Potential reduce by 122.9 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 22.3 kB, which is 16% 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 122.9 kB or 89% of the original size.
Potential reduce by 492 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 10 (67%)
15
5
The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Twitter. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
developer.twitter.com
76 ms
en
43 ms
chirp.css.twhash.a.f.41e1f29c2d4295d68b05db0725781db3.css
40 ms
legacy-colors.css.twhash.a.f.20fd26d638816cbce52d44904fc9c3c2.css
50 ms
project.css.twhash.a.f.9b9b7e2d9404f9e756d0962c03502a4d.css
58 ms
widgets.js
210 ms
core.js.twhash.a.f.fed30134cac6410d0e4ae9b5a78416a3.js
105 ms
project.js.twhash.a.f.6133a61ea33990d0e3ab130309927d99.js
154 ms
clientlib-twtr-profile-adapter.min.twhash.a.cl.c3b119a4cc2249caed364b89790624a4.js
107 ms
clientlib-u12-data-protection-notice.min.twhash.a.cl.8d93205985d36dea4268f79e373e2b02.css
109 ms
clientlib-promise-polyfill.min.twhash.a.cl.678c3c47bfcf62393184734a7204fcdf.js
111 ms
clientlib-twtr-profile-adapter.min.twhash.a.cl.2f6a2e41ae41c33aba9f8a7dcf876eb6.js
112 ms
clientlib-u12-data-protection-notice.min.twhash.a.cl.07841e68cd67e37f7c17e3a5c3c32e2d.js
115 ms
banner-tear-top.svg
14 ms
Chirp-K-Medium.woff
286 ms
Chirp-Devanagari-Web-Medium.woff
263 ms
Chirp-CY-Bold-Web.woff
230 ms
Chirp-A-Medium-Web.woff
327 ms
ChirpTPJ-Medium.woff
454 ms
chirp-bold-web.woff
328 ms
Chirp-K-Regular.woff
328 ms
Chirp-Devanagari-Web-Regular.woff
327 ms
Chirp-CY-Regular-Web.woff
328 ms
Chirp-A-Regular-Web.woff
373 ms
ChirpTPJ-Regular.woff
512 ms
chirp-regular-web.woff
330 ms
print.css.twhash.a.f.67de1c964d9398cbf614aab841910ad6.css
20 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
108 ms
Chirp-K-Heavy.woff
121 ms
Chirp-Devanagari-Web-Heavy.woff
121 ms
Chirp-Display-CY-Extended-Black_Web.woff
161 ms
Chirp-A-Heavy-Web.woff
162 ms
ChirpTPJ-Heavy.woff
220 ms
chirp-display-extended-black-web.woff
162 ms
settings
101 ms
Chirp-SC-Medium.woff
95 ms
Chirp-SC-Regular.woff
213 ms
Chirp-TC-Medium.woff
63 ms
Chirp-TC-Regular.woff
77 ms
twitter.dev accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
twitter.dev best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
twitter.dev SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Twitter.dev 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 Twitter.dev 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.
twitter.dev
Open Graph data is detected on the main page of Twitter. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: