By using site services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.Accept
X

Issues search

https://example.com/
There is no «title» attribute for 212 links.

Links are indicated in the code using the <a> tag. The «title» attribute is important for SEO. Search engines analyze it to understand is the link relevant. Relevant links allow users to receive additional useful information. Search engines understand this and value pages that supplement information with third-party materials.

To fix this, create and fill the «title» attribute for links with relevant content.

Optimizing images for a desktop screen can safe 3.65 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes.

To fix this, upload the image with the correct size.

There is no «alt» attribute for 95 images.

Images are indicated in the code using the <img> tag. To understand whether a picture is an illustration for the page text, search engines analyze the «alt» attribute. Search engines want to show their users articles with relevant illustrations.

To fix it, create and fill the «alt» attribute with relevant content

Buttons are too small for mobile touch.

Too small elements are difficult for touching. An element must have a minimum of 44 pixels height and 44 pixels in width. Users have a problem to touch small elements.

To fix this, adapt your elements for the user's fingers.

Social media and messengers can’t show a beautiful preview for the page.

When users post a link in social media or messengers, the services use some additional data to show a beautiful preview. All that data can be defined using special meta tags.You haven't some required data to show the beautiful snippet.

To fix this:

  1. Install a special plugin to add and edit such data.
  2. Ask the programmer to add this functionality to your site.
Optimizing images for a tab horizontal screen can save 1.18 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes. This is sensitive for mobile devices.

To fix this, use an attribute «srcset» to define various source files.

JavaScript code delays page displaying.

JavaScript files contain program code that makes the web page interactive. It takes time to download and execute this code. If files are attached at the beginning of the page, the page will not be displayed until the JavaScript code is executed.

To prevent this, move all <script> tags to the end of the page before </body> tag.

Tablet users have troubles using horizontal screen orientation.

The typical size of a horizontal tablet screen has a width of 1024 pixels. The page has a large width and dangles right-left when used. Your users will not use a non-convenient site.

To fix this:

  1. Check the page visually. Perhaps some element does not fit on the screen and stretches the page. Typically, this element is a table or image.
  2. Optimize your site for such a screen width.
Unformatted text is found.

The text becomes more readable thanks to headers, images, bold font, etc. Users will close a page with large unformatted blocks of text. Search engines know that and move such pages at the end of the search result page.

To prevent this, split text using headers, bold font, numerated lists, etc.

The meta tag «description» is missing.

Using the «description» tag, you tell the search engine what your page is about, and the search engine tries to show it to interested users. Without a quality «description» tag, you are less likely to be in search results.

To fix this, add and fill the «description» tag with relevant content.

Optimizing images for a tab vertical screen can save 1.14 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes. This is sensitive for mobile devices.

To fix this, use an attribute «srcset» to define various source files.

Optimizing images for a mobile vertical screen can save 1.02 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes. This is sensitive for mobile devices.

To fix this, use an attribute «srcset» to define various source files.

An unsecured connection is still available.

Unsecured connections are available on your site. You need to add the automatic redirection to a secure channel.

To do this:

  1. Edit the «.htaccess» file if available.
  2. Configure Nginx or Apache on your web server for redirection.
  3. Set up redirection in your CMS system or use a special plugin.
  4. Perhaps this feature is in the panel of your hosting provider.
Strict HTTPS header isn't sent.

By accident or upon the initiative of a hacker, your users can send a request to your site by an unprotected channel. At this point, the authorization and identity data can be intercepted.

To prevent this, configure your webserver to send the «Strict-Transport-Security» header. It tells the browser to use only secure connection.

Some functionality can be broken because the page has 1 JavaScript errors.

JavaScript files contain program code that makes the web page interactive. If there are errors in this code, then the functional that it implements does not work.

To fix this:

  1. Perhaps one of the JavaScript files is simply not loaded, because of this, other files throw errors.
  2. Contact a programmer who can fix these errors.
There is no DMARK record.

When you register a domain name, you define minimum 2 DNS servers. They need to inform important data about your site. One of these data is the DMARK record. It tells mailing services the way for reporting about attempts to send email on your behalf. Spam filters can deny your letters without this record.

To prevent this, configure your DNS server using this type of record. Use our DNS generator for that.

Your SSL certificate is self-signed.

The SSL certificate encrypts a connection between users and your web server. No data can be intercepted with this encryption. Your certificate is not certified by any certification center.

To certify a certificate:

  1. Use one of the certification authorities.
  2. Install a free Let's Encrypt certificate.
  3. Perhaps your hosting provider provides services for installing a new SSL certificate in an automatic mode.
There is no high-resolution favicon.

Favicon is an icon that is displayed in a browser tab, search results, and bookmarks. Without it, your site will be difficult to find in the list of other sites. To correctly display on high-resolution screens, you need a 48x48 pixel icon.

To add it:

  1. Add tag <link rel="icon" type="image/png" sizes="48x48" href="/favicon-48x48.png"> in head section for all pages. Attribute «href» is a path to file.
  2. Upload a 48x48 pixel icon on the server.
The icon for Apple devices isn’t found.

Various Apple products need a picture of your site to display it on their interfaces. You can specify several sizes, but just specify the icon with a size 180x180 pixels. It will be enough for use in all programs.

To add it:

  1. Add tag <link rel="apple-touch-icon" sizes="180x180" href="apple-touch-icon-180x180.png"> in head section for all pages.
  2. Upload a 180x180 pixel image by the path defined in the «href» attribute.
Tag <H1> must be one only.

Search engines give high priority to the <H1> tag. Without this tag, search engines will not be able to correctly interpret the content on the page and accordingly predict, which users might be interested in the page.

This tag should be the only one on the page. Otherwise, search engines will lower its priority.

To fix this, remove all <H1> tags except one.

The page isn’t divided into the HTML5 sections.

HTML5 standards require to split a page into sections by tags: <header>, <aside>, <nav> and <footer>. Thanks to them, search engines are much easier to understand the structure of your site and give priority to really important blocks. They can index pages better, more often and faster. It also allows users to use the page in the «Reader View» mode.

To implement this, divide your HTML code using these tags.

Grammar mistakes found.

The <title> tag and/or different meta tags of the page have grammar mistakes. The page can be excluded from the search engine's index.

To prevent this, correct grammar mistakes.

The total image weight of images is 2.21 MB.

The total weight of images on the page should be less than 1 Mb. If your pages weigh a lot, then it will load too long.

To prevent it, use a lazy load to make a user's visit more comfortable.

There is no IPv6 record.

There are 2 types of IP addresses: IPv4 and IPv6. IPv4 address looks like «127.0.0.1» IPv6 looks like «2001:db8::ff00:42:8329». Without the IPv6 address, your site can be unavailable for some users.

To prevent this, configure your webserver to use IPv6 connection.

Page weighs 168.04 KB.

The whole page consists of HTML code. If this code is too much, then the page takes a long time to load. The page should not weigh more than 120Kb.

To fix this:

  1. If the page has pagination then reduce the number of items displayed at once in the list.
  2. Use dynamically loaded content. Such content is loaded when the user scrolls the page.
  3. Simplify the HTML code of the page, if possible.
There is no reverse DNS record.

Reverse DNS or rDNS record is needed to inform, which domain name is associated with defined IP. The sites with rDNS record is more trusted. Spam filters can deny your letters without this record.

To prevent this, define an rDNS record for your server. Usually, you can do that in the hosting management cabinet.

The page doesn't have integration with Android devices.

Various Android devices need a picture of your site to display it in their interfaces. Without it, users will see a poor auto-generated icon on their devices. The «manifest.json» file describes such images and provides a download link.Information about this file is missing.

To fix this:

  1. Build the «manifest.json» file. Read how to do this in the article or documentation from the Android.
  2. Add a tag <link rel="manifest" href="/manifest.json"> in head section for all pages. Attribute «href» is a path to the file.
The page doesn't have integration with Microsoft programs.

Various Microsoft products need a picture of your site to display it in their interfaces. The «Browserconfig.xml» file describes such images and provides a link to download. Without it, users will see a poor auto-generated icon on their devices.The file isn't found.

To add it:

  1. Generate a file. How to do this, read the article or documentation from Microsoft.
  2. Add a tag to all pages «/browserconfg.xml» file from tag <meta name="msapplication-config" content="/browserconfg.xml" />. The attribute «content» contains the path to the file.
Too small images for a mobile screen are found.

The source image size doesn't match to displayed size. The small size of the source file makes the image look blurred.

To fix this, use an attribute «srcset» to define various source files.

Stretched images on a desktop screen are found.

If you see an oval and rectangular shape on the image instead of round and square, this means that the image is stretched. It looks poor and spoils the impression of the site.

To fix this, resize the source image or fix the CSS style of the image element.

Stretched images on mobile screens are found.

If you see an oval and rectangular shape on the image instead of round and square, this means that the image is stretched. It looks poor and spoils the impression of the site.

To fix this, resize the source image or fix the CSS style of the image element.

Your site uses unknown structured data.

Structured data formatting allows your website pages to be displayed in the search results with a more beautiful and clickable snippet. Without it, your competitors will jump you.

You are using structured data that can't be used by Google.

To fix this, check the structured data block for correctness.

Found 31 cycled links on the page.

If the link leads to the page on which it is located, then it is called cyclic. When you click on such a link, the user loses time and feels discomfort.

To prevent this, remove links that follow to themselves.

https://example.com/?add-to-cart=36
There is no «title» attribute for 216 links.

Links are indicated in the code using the <a> tag. The «title» attribute is important for SEO. Search engines analyze it to understand is the link relevant. Relevant links allow users to receive additional useful information. Search engines understand this and value pages that supplement information with third-party materials.

To fix this, create and fill the «title» attribute for links with relevant content.

Optimizing images for a desktop screen can safe 3.64 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes.

To fix this, upload the image with the correct size.

There is no «alt» attribute for 96 images.

Images are indicated in the code using the <img> tag. To understand whether a picture is an illustration for the page text, search engines analyze the «alt» attribute. Search engines want to show their users articles with relevant illustrations.

To fix it, create and fill the «alt» attribute with relevant content

Buttons are too small for mobile touch.

Too small elements are difficult for touching. An element must have a minimum of 44 pixels height and 44 pixels in width. Users have a problem to touch small elements.

To fix this, adapt your elements for the user's fingers.

Social media and messengers can’t show a beautiful preview for the page.

When users post a link in social media or messengers, the services use some additional data to show a beautiful preview. All that data can be defined using special meta tags.You haven't some required data to show the beautiful snippet.

To fix this:

  1. Install a special plugin to add and edit such data.
  2. Ask the programmer to add this functionality to your site.
Optimizing images for a tab horizontal screen can save 1.18 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes. This is sensitive for mobile devices.

To fix this, use an attribute «srcset» to define various source files.

JavaScript code delays page displaying.

JavaScript files contain program code that makes the web page interactive. It takes time to download and execute this code. If files are attached at the beginning of the page, the page will not be displayed until the JavaScript code is executed.

To prevent this, move all <script> tags to the end of the page before </body> tag.

Tablet users have troubles using horizontal screen orientation.

The typical size of a horizontal tablet screen has a width of 1024 pixels. The page has a large width and dangles right-left when used. Your users will not use a non-convenient site.

To fix this:

  1. Check the page visually. Perhaps some element does not fit on the screen and stretches the page. Typically, this element is a table or image.
  2. Optimize your site for such a screen width.
Unformatted text is found.

The text becomes more readable thanks to headers, images, bold font, etc. Users will close a page with large unformatted blocks of text. Search engines know that and move such pages at the end of the search result page.

To prevent this, split text using headers, bold font, numerated lists, etc.

The meta tag «description» is missing.

Using the «description» tag, you tell the search engine what your page is about, and the search engine tries to show it to interested users. Without a quality «description» tag, you are less likely to be in search results.

To fix this, add and fill the «description» tag with relevant content.

Optimizing images for a tab vertical screen can save 1.14 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes. This is sensitive for mobile devices.

To fix this, use an attribute «srcset» to define various source files.

Optimizing images for a mobile vertical screen can save 1.02 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes. This is sensitive for mobile devices.

To fix this, use an attribute «srcset» to define various source files.

Some functionality can be broken because the page has 1 JavaScript errors.

JavaScript files contain program code that makes the web page interactive. If there are errors in this code, then the functional that it implements does not work.

To fix this:

  1. Perhaps one of the JavaScript files is simply not loaded, because of this, other files throw errors.
  2. Contact a programmer who can fix these errors.
The page’s title isn’t unique.

You have duplicated page titles. By this reason, search engines may exclude one of the pages from the search results.

To prevent this, change a title for one of the pages to unique relevant text.

There is no high-resolution favicon.

Favicon is an icon that is displayed in a browser tab, search results, and bookmarks. Without it, your site will be difficult to find in the list of other sites. To correctly display on high-resolution screens, you need a 48x48 pixel icon.

To add it:

  1. Add tag <link rel="icon" type="image/png" sizes="48x48" href="/favicon-48x48.png"> in head section for all pages. Attribute «href» is a path to file.
  2. Upload a 48x48 pixel icon on the server.
The icon for Apple devices isn’t found.

Various Apple products need a picture of your site to display it on their interfaces. You can specify several sizes, but just specify the icon with a size 180x180 pixels. It will be enough for use in all programs.

To add it:

  1. Add tag <link rel="apple-touch-icon" sizes="180x180" href="apple-touch-icon-180x180.png"> in head section for all pages.
  2. Upload a 180x180 pixel image by the path defined in the «href» attribute.
Tag <H1> must be one only.

Search engines give high priority to the <H1> tag. Without this tag, search engines will not be able to correctly interpret the content on the page and accordingly predict, which users might be interested in the page.

This tag should be the only one on the page. Otherwise, search engines will lower its priority.

To fix this, remove all <H1> tags except one.

The page isn’t divided into the HTML5 sections.

HTML5 standards require to split a page into sections by tags: <header>, <aside>, <nav> and <footer>. Thanks to them, search engines are much easier to understand the structure of your site and give priority to really important blocks. They can index pages better, more often and faster. It also allows users to use the page in the «Reader View» mode.

To implement this, divide your HTML code using these tags.

Grammar mistakes found.

The <title> tag and/or different meta tags of the page have grammar mistakes. The page can be excluded from the search engine's index.

To prevent this, correct grammar mistakes.

The total image weight of images is 2.19 MB.

The total weight of images on the page should be less than 1 Mb. If your pages weigh a lot, then it will load too long.

To prevent it, use a lazy load to make a user's visit more comfortable.

Page weighs 169.68 KB.

The whole page consists of HTML code. If this code is too much, then the page takes a long time to load. The page should not weigh more than 120Kb.

To fix this:

  1. If the page has pagination then reduce the number of items displayed at once in the list.
  2. Use dynamically loaded content. Such content is loaded when the user scrolls the page.
  3. Simplify the HTML code of the page, if possible.
The page doesn't have integration with Android devices.

Various Android devices need a picture of your site to display it in their interfaces. Without it, users will see a poor auto-generated icon on their devices. The «manifest.json» file describes such images and provides a download link.Information about this file is missing.

To fix this:

  1. Build the «manifest.json» file. Read how to do this in the article or documentation from the Android.
  2. Add a tag <link rel="manifest" href="/manifest.json"> in head section for all pages. Attribute «href» is a path to the file.
The page doesn't have integration with Microsoft programs.

Various Microsoft products need a picture of your site to display it in their interfaces. The «Browserconfig.xml» file describes such images and provides a link to download. Without it, users will see a poor auto-generated icon on their devices.The file isn't found.

To add it:

  1. Generate a file. How to do this, read the article or documentation from Microsoft.
  2. Add a tag to all pages «/browserconfg.xml» file from tag <meta name="msapplication-config" content="/browserconfg.xml" />. The attribute «content» contains the path to the file.
Too small images for a mobile screen are found.

The source image size doesn't match to displayed size. The small size of the source file makes the image look blurred.

To fix this, use an attribute «srcset» to define various source files.

Stretched images on a desktop screen are found.

If you see an oval and rectangular shape on the image instead of round and square, this means that the image is stretched. It looks poor and spoils the impression of the site.

To fix this, resize the source image or fix the CSS style of the image element.

Stretched images on mobile screens are found.

If you see an oval and rectangular shape on the image instead of round and square, this means that the image is stretched. It looks poor and spoils the impression of the site.

To fix this, resize the source image or fix the CSS style of the image element.

Your site uses unknown structured data.

Structured data formatting allows your website pages to be displayed in the search results with a more beautiful and clickable snippet. Without it, your competitors will jump you.

You are using structured data that can't be used by Google.

To fix this, check the structured data block for correctness.

Found 1 cycled links on the page.

If the link leads to the page on which it is located, then it is called cyclic. When you click on such a link, the user loses time and feels discomfort.

To prevent this, remove links that follow to themselves.

https://example.com/?remove_item=19ca14e7ea6328a42e0eb13d585e4c22&_wpnonce=8b1f212561
There is no «title» attribute for 212 links.

Links are indicated in the code using the <a> tag. The «title» attribute is important for SEO. Search engines analyze it to understand is the link relevant. Relevant links allow users to receive additional useful information. Search engines understand this and value pages that supplement information with third-party materials.

To fix this, create and fill the «title» attribute for links with relevant content.

Optimizing images for a desktop screen can safe 3.64 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes.

To fix this, upload the image with the correct size.

There is no «alt» attribute for 95 images.

Images are indicated in the code using the <img> tag. To understand whether a picture is an illustration for the page text, search engines analyze the «alt» attribute. Search engines want to show their users articles with relevant illustrations.

To fix it, create and fill the «alt» attribute with relevant content

Buttons are too small for mobile touch.

Too small elements are difficult for touching. An element must have a minimum of 44 pixels height and 44 pixels in width. Users have a problem to touch small elements.

To fix this, adapt your elements for the user's fingers.

Optimizing images for a mobile horizontal screen can save 2.91 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes. This is sensitive for mobile devices.

To fix this, use an attribute «srcset» to define various source files.

Social media and messengers can’t show a beautiful preview for the page.

When users post a link in social media or messengers, the services use some additional data to show a beautiful preview. All that data can be defined using special meta tags.You haven't some required data to show the beautiful snippet.

To fix this:

  1. Install a special plugin to add and edit such data.
  2. Ask the programmer to add this functionality to your site.
Optimizing images for a tab horizontal screen can save 1.18 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes. This is sensitive for mobile devices.

To fix this, use an attribute «srcset» to define various source files.

JavaScript code delays page displaying.

JavaScript files contain program code that makes the web page interactive. It takes time to download and execute this code. If files are attached at the beginning of the page, the page will not be displayed until the JavaScript code is executed.

To prevent this, move all <script> tags to the end of the page before </body> tag.

Tablet users have troubles using horizontal screen orientation.

The typical size of a horizontal tablet screen has a width of 1024 pixels. The page has a large width and dangles right-left when used. Your users will not use a non-convenient site.

To fix this:

  1. Check the page visually. Perhaps some element does not fit on the screen and stretches the page. Typically, this element is a table or image.
  2. Optimize your site for such a screen width.
Unformatted text is found.

The text becomes more readable thanks to headers, images, bold font, etc. Users will close a page with large unformatted blocks of text. Search engines know that and move such pages at the end of the search result page.

To prevent this, split text using headers, bold font, numerated lists, etc.

The meta tag «description» is missing.

Using the «description» tag, you tell the search engine what your page is about, and the search engine tries to show it to interested users. Without a quality «description» tag, you are less likely to be in search results.

To fix this, add and fill the «description» tag with relevant content.

Optimizing images for a tab vertical screen can save 1.14 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes. This is sensitive for mobile devices.

To fix this, use an attribute «srcset» to define various source files.

Optimizing images for a mobile vertical screen can save 1.02 MB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes. This is sensitive for mobile devices.

To fix this, use an attribute «srcset» to define various source files.

Some functionality can be broken because the page has 1 JavaScript errors.

JavaScript files contain program code that makes the web page interactive. If there are errors in this code, then the functional that it implements does not work.

To fix this:

  1. Perhaps one of the JavaScript files is simply not loaded, because of this, other files throw errors.
  2. Contact a programmer who can fix these errors.
The page’s title isn’t unique.

You have duplicated page titles. By this reason, search engines may exclude one of the pages from the search results.

To prevent this, change a title for one of the pages to unique relevant text.

There is no high-resolution favicon.

Favicon is an icon that is displayed in a browser tab, search results, and bookmarks. Without it, your site will be difficult to find in the list of other sites. To correctly display on high-resolution screens, you need a 48x48 pixel icon.

To add it:

  1. Add tag <link rel="icon" type="image/png" sizes="48x48" href="/favicon-48x48.png"> in head section for all pages. Attribute «href» is a path to file.
  2. Upload a 48x48 pixel icon on the server.
The icon for Apple devices isn’t found.

Various Apple products need a picture of your site to display it on their interfaces. You can specify several sizes, but just specify the icon with a size 180x180 pixels. It will be enough for use in all programs.

To add it:

  1. Add tag <link rel="apple-touch-icon" sizes="180x180" href="apple-touch-icon-180x180.png"> in head section for all pages.
  2. Upload a 180x180 pixel image by the path defined in the «href» attribute.
Tag <H1> must be one only.

Search engines give high priority to the <H1> tag. Without this tag, search engines will not be able to correctly interpret the content on the page and accordingly predict, which users might be interested in the page.

This tag should be the only one on the page. Otherwise, search engines will lower its priority.

To fix this, remove all <H1> tags except one.

The page isn’t divided into the HTML5 sections.

HTML5 standards require to split a page into sections by tags: <header>, <aside>, <nav> and <footer>. Thanks to them, search engines are much easier to understand the structure of your site and give priority to really important blocks. They can index pages better, more often and faster. It also allows users to use the page in the «Reader View» mode.

To implement this, divide your HTML code using these tags.

Grammar mistakes found.

The <title> tag and/or different meta tags of the page have grammar mistakes. The page can be excluded from the search engine's index.

To prevent this, correct grammar mistakes.

The total image weight of images is 2.19 MB.

The total weight of images on the page should be less than 1 Mb. If your pages weigh a lot, then it will load too long.

To prevent it, use a lazy load to make a user's visit more comfortable.

Page weighs 168.03 KB.

The whole page consists of HTML code. If this code is too much, then the page takes a long time to load. The page should not weigh more than 120Kb.

To fix this:

  1. If the page has pagination then reduce the number of items displayed at once in the list.
  2. Use dynamically loaded content. Such content is loaded when the user scrolls the page.
  3. Simplify the HTML code of the page, if possible.
The page doesn't have integration with Android devices.

Various Android devices need a picture of your site to display it in their interfaces. Without it, users will see a poor auto-generated icon on their devices. The «manifest.json» file describes such images and provides a download link.Information about this file is missing.

To fix this:

  1. Build the «manifest.json» file. Read how to do this in the article or documentation from the Android.
  2. Add a tag <link rel="manifest" href="/manifest.json"> in head section for all pages. Attribute «href» is a path to the file.
The page doesn't have integration with Microsoft programs.

Various Microsoft products need a picture of your site to display it in their interfaces. The «Browserconfig.xml» file describes such images and provides a link to download. Without it, users will see a poor auto-generated icon on their devices.The file isn't found.

To add it:

  1. Generate a file. How to do this, read the article or documentation from Microsoft.
  2. Add a tag to all pages «/browserconfg.xml» file from tag <meta name="msapplication-config" content="/browserconfg.xml" />. The attribute «content» contains the path to the file.
Too small images for a mobile screen are found.

The source image size doesn't match to displayed size. The small size of the source file makes the image look blurred.

To fix this, use an attribute «srcset» to define various source files.

Stretched images on a desktop screen are found.

If you see an oval and rectangular shape on the image instead of round and square, this means that the image is stretched. It looks poor and spoils the impression of the site.

To fix this, resize the source image or fix the CSS style of the image element.

Stretched images on mobile screens are found.

If you see an oval and rectangular shape on the image instead of round and square, this means that the image is stretched. It looks poor and spoils the impression of the site.

To fix this, resize the source image or fix the CSS style of the image element.

Your site uses unknown structured data.

Structured data formatting allows your website pages to be displayed in the search results with a more beautiful and clickable snippet. Without it, your competitors will jump you.

You are using structured data that can't be used by Google.

To fix this, check the structured data block for correctness.

https://example.com/?product=women-white-shirt
There is no «title» attribute for 71 links.

Links are indicated in the code using the <a> tag. The «title» attribute is important for SEO. Search engines analyze it to understand is the link relevant. Relevant links allow users to receive additional useful information. Search engines understand this and value pages that supplement information with third-party materials.

To fix this, create and fill the «title» attribute for links with relevant content.

Optimizing images for a desktop screen can safe 36.76 KB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes.

To fix this, upload the image with the correct size.

Buttons are too small for mobile touch.

Too small elements are difficult for touching. An element must have a minimum of 44 pixels height and 44 pixels in width. Users have a problem to touch small elements.

To fix this, adapt your elements for the user's fingers.

There is no «alt» attribute for 24 images.

Images are indicated in the code using the <img> tag. To understand whether a picture is an illustration for the page text, search engines analyze the «alt» attribute. Search engines want to show their users articles with relevant illustrations.

To fix it, create and fill the «alt» attribute with relevant content

Social media and messengers can’t show a beautiful preview for the page.

When users post a link in social media or messengers, the services use some additional data to show a beautiful preview. All that data can be defined using special meta tags.You haven't some required data to show the beautiful snippet.

To fix this:

  1. Install a special plugin to add and edit such data.
  2. Ask the programmer to add this functionality to your site.
Optimizing images for a tab horizontal screen can save 133.98 KB.

The source image size doesn't match to displayed size. Big source file makes users download extra kilobytes. This is sensitive for mobile devices.

To fix this, use an attribute «srcset» to define various source files.

JavaScript code delays page displaying.

JavaScript files contain program code that makes the web page interactive. It takes time to download and execute this code. If files are attached at the beginning of the page, the page will not be displayed until the JavaScript code is executed.

To prevent this, move all <script> tags to the end of the page before </body> tag.

Tablet users have troubles using horizontal screen orientation.

The typical size of a horizontal tablet screen has a width of 1024 pixels. The page has a large width and dangles right-left when used. Your users will not use a non-convenient site.

To fix this:

  1. Check the page visually. Perhaps some element does not fit on the screen and stretches the page. Typically, this element is a table or image.
  2. Optimize your site for such a screen width.
Forms are unsafe.

Some forms on your site are available for sending unauthorized requests. Use CSFR protection to secure your web forms. Without it, your site is vulnerable to cyber-attacks.

To fix this, change code or use a ready plugin to implement CSFR protection.

Unformatted text is found.

The text becomes more readable thanks to headers, images, bold font, etc. Users will close a page with large unformatted blocks of text. Search engines know that and move such pages at the end of the search result page.

To prevent this, split text using headers, bold font, numerated lists, etc.

The meta tag «description» is missing.

Using the «description» tag, you tell the search engine what your page is about, and the search engine tries to show it to interested users. Without a quality «description» tag, you are less likely to be in search results.

To fix this, add and fill the «description» tag with relevant content.