Att.net Site Title

Currently.com - AT&T Yahoo Email, News, Sports & More

Att.net Meta Description

Get the latest in news, entertainment, sports, weather and more on Currently.com. Sign up for free email service with AT&T Yahoo Mail.

Att.net Test Results

Att.net Mobile Performance: 0/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused CSS. Potential savings of 44 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Remove unused JavaScript. Potential savings of 23 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Avoid multiple page redirects. 0 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Defer offscreen images. 0 ms
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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 270 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
3.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Serve static assets with an efficient cache policy
27 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
JavaScript execution time
1.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid long main-thread tasks
13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. 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
100 requests • 812 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Budgets
Performance budgets set standards for the performance of your site.
Timing budget
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more.

Att.net Mobile SEO: 83/100
Quick overview:
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.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more. Lighthouse was unable to download a robots.txt file

Att.net Mobile Best Practices: 77/100
Quick overview:
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. 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.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Document must contain a doctype
Att.net Mobile Progressive Web App: 0/100
Quick overview:
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched.
Does not provide fallback content when JavaScript is not available
Your app should display some content when JavaScript is disabled, even if it's just a warning to the user that JavaScript is required to use the app. Learn more. The page body should render some content if its scripts are not available.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Fast and reliable
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Page load is fast enough on mobile networks
A fast page load over a cellular network ensures a good mobile user experience. Learn more.
Installable
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
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.
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Att.net Mobile Accessibility: 45/100
Quick overview:
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. 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.
Similar tests
www.att.com
www.att.net
www.att.org
www.att.info
www.att.biz
www.att.us
www.att.mobi
www.tt.net
www.att.net
www.qtt.net
www.aqtt.net
www.qatt.net
www.wtt.net
www.awtt.net
www.watt.net
www.stt.net
www.astt.net
www.satt.net
www.ztt.net
www.aztt.net
www.zatt.net
www.at.net
www.art.net
www.atrt.net
www.artt.net
www.aft.net
www.atft.net
www.aftt.net
www.agt.net
www.atgt.net
www.agtt.net
www.ayt.net
www.atyt.net
www.aytt.net
www.atr.net
www.attr.net
www.atf.net
www.attf.net
www.atg.net
www.attg.net
www.aty.net
www.atty.net
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.