In order to pass this test you must create a sitemap.xml file for your website. Some of the best practices are listed below:

• It is strongly recommended that you place your sitemap at the root directory of your website: http://yourwebsite.com/sitemap.xml But in some situations, you may want to produce different sitemaps for different paths on your site (e.g., security permission issues)
• Sitemaps should be no larger than 10MB (10,485,760 bytes) and can contain a maximum of 50,000 URLs. This means that if your site contains more than 50,000 URLs or your sitemap is bigger than 10MB, you must create multiple sitemap files and use a Sitemap index file
• All URLs listed in the sitemap must reside on the same host as the sitemap. For instance, if the sitemap is located at http://www.yourwebsite.com/sitemap.xml, it can't include URLs from http://subdomain.yourwebsite.com
• Once you have created your sitemap, let search engines know about it by submitting directly to them, pinging them, or adding the sitemap location to your robots.txt file
• Sitemaps can be compressed using gzip, reducing bandwidth consumption

sitemap.xml example:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
 <loc>http://www.yourwebsite.com</loc>
 <lastmod>2013-01-01</lastmod>
 <changefreq>weekly</changefreq>
 <priority>0.9</priority>
</url>
<url>
 <loc>http://www.yourwebsite.com/articles/100</loc>
 <changefreq>weekly</changefreq>
</url>
<url>
 <loc>http://www.yourwebsite.com/articles/101</loc>
 <lastmod>2013-01-02</lastmod>
 <changefreq>weekly</changefreq>
</url>
<url>
 <loc>http://www.yourwebsite.com/articles/102</loc>
 <lastmod>2013-01-02T13:00:12+00:00</lastmod>
 <priority>0.5</priority>
</url>
</urlset>

In order to pass this test you must add an alt attribute to every <img> tag used into your webpage.

An image with an alternate text specified is inserted using the following HTML line:

<img src="image.png" alt="text_to_describe_your_image">

Remember that the point of alt text is to provide the same functional information that a visual user would see. Search engines, users who disabled images in their browsers and other agents who are unable to see the images on your webpage can read the alt attributes assigned to the image since they cannot view it.

Learn more about optimizing images for SEO.

In order to resolve this problem you are advised to:

• use gzip compression
• move all CSS style rules into a single, external and minified CSS file
• minify all JS files and, if possible, try combining them into a single external JS file
• use CSS layouts

In order to pass this test, you need to reduce the DOM size.

First, you need to identify the causes of an excessive number of DOM nodes. They can be: poorly coded plugins or themes, DOM nodes created dynamically via JavaScript, page builders that generate bloated HTML, copy-paste text into a WYSIWYG editor, hidden elements via CSS, etc.

Second, you need to remove the unnecessary tags and even refactor or rewrite some parts of the code/template. Another workarounds can be: code splitting (create more pages instead of one long page), consider to lazy load some parts of your website in order to speed up the initial rendering, implement infinite scroll, improve page rendering with content visibility (with the CSS content-visibility property, the browser will skip the styling, layout, and paint until the user scrolls down the page).

In order to pass this test you have to decrease the JavaScript code execution time. You can do this by:

- implementing code-splitting: split the JavaScript bundle into smaller files so that only the critical code is executed during initial page load.

- removing unused code: unused code can often be inherited from previous versions of your site, and/or imported from other modules that aren't referenced anymore.

- reduce network trips by caching your code with the PRPL pattern: preload the most important resources, render the initial route as soon as possible, pre-cache remaining assets and lazy load other routes and non-critical assets.

- minifying and compressing the JavaScript code

In order to pass this test, you have to remove the unnecessary image metadata (additional information which is stored along with the image). There are literally hundreds of metadata tags, but most of them (like camera model and settings, exposure, creation date, etc) are useless to site visitors and isn't required by browsers to render images. However, a few metadata tags can still be useful and may help Search Engine bots to better understand your images:

• GPS tags - These define where the image was taken providing location information that might help with local SEO. If you have a location-based business, tag your image with the GPS coordinates of your premises.
• Author/Owner Name - Add your brand name (or your own name) here because it may influence the image being shown when someone searches your brand in Google Images.
• Image Description - Just like an ALT description, the image description metadata tag can provide information pertaining to what the content of the image is about.

<IfModule mod_expires.c>
    ExpiresActive on
 
    ExpiresByType image/jpg "access plus 1 month"
    ExpiresByType image/jpeg "access plus 1 month"
    ExpiresByType image/gif "access plus 1 month"
    ExpiresByType image/png "access plus 1 month"
</IfModule>

In order to pass this test you must make your email addresses invisible to email spiders. Note that the best option is to replace your entire contact mechanism with a contact form and using the POST method while submitting the form.

Other solutions are listed below:

• replace the at (@) and dot (.) characters
• replace text with images
• use email obfuscators
• hide email addresses using JavaScript or CSS trick

In order to pass this test, you have to update each link identified in this report, by adding a rel="noopener" or a rel="noreferrer" attribute or both:

<a href="https://example.com" target="_blank" rel="noopener noreferrer">
	Click here
</a>

• rel="noopener" prevents the new page from being able to access the window.opener property and ensures it runs in a separate process.
• rel="noreferrer" has the same effect but also prevents the Referer header from being sent to the new page.