5. Reduce DNS lookup time
DNS lookup time is the time it takes to resolve a domain name to its IP address. This IP address is then used to find the location of a server on the Internet.
When a user visits a page, the first high-latency task the browser performs is a DNS lookup of the domain name. Unless the browser gets the IP address from the DNS query, it cannot proceed to connect to the server and make the request.
Ideally, reducing DNS lookup time should be part of a Time-to-First-Byte optimization strategy, but it seems that the PageSpeed tool doesn't take it into account because in many cases it's impossible for webmasters algeria mobile database to optimize in this regard. As a result, a large number of webmasters don't bother with the performance of their DNS providers.
By using a fast DNS provider. As listed in the screenshot above from the DNS benchmarking service DNSPerf.com , there are several services that offer global average latencies of less than 30 milliseconds, fast enough to make DNS lookups imperceptible.
Cache DNS responses with a higher TTL. DNS recursive resolvers can cache these responses close to end users around the world and can further significantly reduce DNS lookup times for all users they serve.
6. Leverage browser caching for fonts
You might get a score of 95 or 98 instead of 100 because of a Google font that a plugin or theme uses on your site, and you might think there's nothing you can do to improve your score in this regard; there is more than one solution to this problem.
Google Fonts CSS only has a 1 day expiration period. This is a feature rather than a bug, as it allows the Google Fonts team to propagate changes to end users faster. However, the problem is that the PageSpeed tool expects you to use a 30 day cache for static assets.