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 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 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

Creating a custom 404 error page can be relatively simple or more complicated, depending on what technologies were used to build your website (your web server, framework used, etc). Learn more about the basics of creating a custom 404 error page.

On your custom error page, you should provide relevant information to keep the user's attention so they remain on your website. Some steps to achieve this goal include:

• Adding links to your most important pages (your best articles articles/content, latest posts, etc.)
• If you have an e-commerce business, you can display special offers, product recommendations, discounts, etc.
• Include a search box or a sitemap link to help users find the information they wanted.
• Use simple language (non-technical) to explain what went wrong.
• Add a contact form or provide an email address to allow users to get in touch with you for further help.

You can also use your custom 404 error page to track the source of broken links in your site.