WordPress Page Optimization Pt. 3
LiteSpeed Cache HTML Settings
Continuing with the 3rd part on LiteSpeed Cache Page Optimization.
You can read out on Pt.1 here
You can read out on Pt. 2 here
Starting off with 3rd tab HTML Settings enable/disable the following:
- HTML Minify
Removes unncessary characters from the HTML code.
Why to enable or disable this?
Enabling this will reduce the size of the HTML file. Disabling it can help developers troubleshoot.
2. DNS Prefetch
Before a browser can communicate it needs to fetch for a DNS lookup, then only the website content is loaded.
Why enable or disable this?
Enabling it, your browser will contain a list of DNS (websites) that it needs to lookup for external resource. Disable this can help reduce the DNS lookup process.
3. DNS Prefetch Control
This allows the users to manually specify domains.
Why enable or disable this?
Enabling this can help reduce the DNS lookup latency. Disable it, since not every external DNS is not required.
4. DNS Preconnect
It closely relates to Prefetch DNS, but more than that, with preconnect, not only it prefetch but the browser also establish a secure connection.
Why enable or disable this?
Enabling Preconnect can reduce the time required to establish a connection to an important third-party resource. Disabling Preconnect will cost a connection problem, therefore leave it enabled.
5. HTML Lazy Load Selectors
Leave it as default.
Get Muhammad Muntiqa’s stories in your inbox
Join Medium for free to get updates from this writer.
6. HTML Keep Comments
When HTML Minify is enabled, LiteSpeed removes HTML comments as part of the minification process.
7. Remove Query Strings
URLs such as “style.css?ver=6.8” or “script.css?ver=7.2”
For the above the string ‘?’ is used to determine the version number.
Why enable or disable this?
Enabling this will increase the load on the browser. Disabling this saves up the browser speed.
8. Load Google Fonts Asynchronously
Websites frequently load fonts from Google Fonts.
Without optimization, a Google Font stylesheet can become part of the resources the browser needs to process while rendering the page.
Why enable or disable this?
Enabling this will load up the correct fonts for the website when rendered. Disabling this can mess up with the fonts.
9. Remove Google Fonts
This option removes all Google fonts from the website (if any).
Why enable or disable this?
Enable it, when there are a lot of external Google fonts, keep it disabled it there are none.
10. Remove WordPress Emoji
WordPress includes additional JavaScript to provide emoji support for older browsers.
Why enable or disable this?
Recommended to keep it enable, since most of the users uses modern browsers, but provides very little practical value.
11. Remove Noscript Tags
The <noscript> tag provides an alternative information when the JS is not available.
Why enable or disable this?
Enabling it can help reduce the amount of HTML sent to the browser. Disabling it is a trade-off with compatibility.
HTML optimization is generally less dangerous than aggressive JavaScript optimization (that we covered in Pt. 2), but that doesn’t mean every option should simply be enabled without testing.
If you found this article helpful, make sure to like and share it with your network as this helps me with the algorithm.
