Twitter.com Test Results

Twitter.com Mobile Performance: 25/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript. Potential savings of 302 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Serve images in next-gen formats. Potential savings of 191 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Avoid multiple page redirects. Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Efficiently encode images. Potential savings of 160 KiB
Optimized images load faster and consume less cellular data. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,310 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Minimize main-thread work
5.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
3.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid chaining critical requests
1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Keep request counts low and transfer sizes small
35 requests • 1,118 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks
16 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
User Timing marks and measures
1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More

Twitter.com Mobile SEO: 91/100
Quick overview:
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.
Tap targets are not sized appropriately
88% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.

Twitter.com Mobile Best Practices: 85/100
Quick overview:
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Twitter.com Mobile Progressive Web App: 93/100
Quick overview:
Installable
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Twitter.com Mobile Accessibility: 71/100
Quick overview:
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.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
`[role]`s do not have all required `[aria-*]` attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn more.
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar sites
Similar tests
www.twitter.com
www.twitter.net
www.twitter.org
www.twitter.info
www.twitter.biz
www.twitter.us
www.twitter.mobi
www.witter.com
www.twitter.com
www.rwitter.com
www.trwitter.com
www.rtwitter.com
www.fwitter.com
www.tfwitter.com
www.ftwitter.com
www.gwitter.com
www.tgwitter.com
www.gtwitter.com
www.ywitter.com
www.tywitter.com
www.ytwitter.com
www.titter.com
www.tqitter.com
www.twqitter.com
www.tqwitter.com
www.taitter.com
www.twaitter.com
www.tawitter.com
www.tsitter.com
www.twsitter.com
www.tswitter.com
www.teitter.com
www.tweitter.com
www.tewitter.com
www.twtter.com
www.twutter.com
www.twiutter.com
www.twuitter.com
www.twjtter.com
www.twijtter.com
www.twjitter.com
www.twktter.com
www.twiktter.com
www.twkitter.com
www.twotter.com
www.twiotter.com
www.twoitter.com
www.twiter.com
www.twirter.com
www.twitrter.com
www.twirtter.com
www.twifter.com
www.twitfter.com
www.twiftter.com
www.twigter.com
www.twitgter.com
www.twigtter.com
www.twiyter.com
www.twityter.com
www.twiytter.com
www.twitrer.com
www.twittrer.com
www.twitfer.com
www.twittfer.com
www.twitger.com
www.twittger.com
www.twityer.com
www.twittyer.com
www.twittr.com
www.twittwr.com
www.twittewr.com
www.twittwer.com
www.twittsr.com
www.twittesr.com
www.twittser.com
www.twittdr.com
www.twittedr.com
www.twittder.com
www.twittrr.com
www.twitterr.com
www.twitte.com
www.twittee.com
www.twittere.com
www.twitteer.com
www.twitted.com
www.twitterd.com
www.twittef.com
www.twitterf.com
www.twittefr.com
www.twittet.com
www.twittert.com
www.twittetr.com
www.twitter.con
Last Tested: