AT&T is the world’s largest telecommunications company and the third-largest mobile telephony services provider in the United States. It is headquartered in Dallas, Texas.
A speed report from Lighthouse paints a rather grim picture and scores AT&T’s website 8.6 seconds on the speed index (SI), and 28 on Performance.
There are many reasons why the AT&T website is so slow. This includes:
- Unused CSS files
- Render-blocking resources
- Slow server
- Large DOM size
Let’s look at each of these reasons and identify potential ways that AT&T can make its website load faster.
But before we do that, a quick word about our website CWVIQ.com - we are a free email alert service that sends out notification any time your website is loading very slowly (often due to heavy traffic, or poor scripts). If you have a website, consider setting up an alert so that you can fix issues before they become major.
The AT&T website can be as much as 4.5 seconds faster by adopting this technique.
Unused CSS files
AT&T uses CSS files to load the styling elements for the website. However, this file contains a lot of unused scripts that can be slowing down page loading by as much as 1.2 seconds. Code splitting may help avoid this issue.
There are scripts on the AT&T website that need to run first before they let the rest of the code be executed. The render-blocking resources issue can shave off around 0.76 seconds from the loading time for the AT&T website.
How do you avoid this? If the script is not critical, avoid having it in the <head> tag of your HTML code. But if you do need to have it there for some reason, make sure to include the defer or async attribute so that they do not block the loading of other resources.
According to the Lighthouse report, a slow server may be contributing to nearly 1.07 seconds of additional loading time. In addition to upgrading the server hardware and database systems, AT&T should also look into the server’s application logic to prepare pages faster.
Large DOM size
The AT&T website takes close to 23.7 seconds to evaluate all the scripts, parse them, compile, and render them. This can be minimized by minimizing the main-thread work.
They may also look at reducing the number of nodes in the DOM. In simpler terms, you need to make sure that the main HTML code is smaller and has fewer nodes. I have explained this in greater detail in this article about DOMContentLoaded.
Anand Srinivasan is the founder of CWVIQ. He is a digital marketing consultant with over 15 years of experience. Anand’s articles have been published on Entrepreneur, GoDaddy, and Business.com to mention a few.