Nibbler SEO audit for absolon.blog.idnes.cz
Summary
Overall9.1
The overall score for this website.
Accessibility8.7
How accessible the website is to mobile and disabled users.
The following tests contribute to this score:
Experience8.8
How satisfying the website is likely to be for users.
The following tests contribute to this score:
Marketing9.5
How well marketed, and popular the website is.
The following tests contribute to this score:
Technology8.7
How well designed and built the website is.
The following tests contribute to this score:
Nibbler tested a sample of 5 pages from this website at 17:20 on 4 Apr 2024 (BST).
Top priorities for website improvement
- Consider URL rewriting as an effective and transparent means of creating appropriate URLs. URLs using unusual characters (such as semi-colons or underscores), long numerals or complex phrasing are very difficult for real people to use or exchange. They also tend to be less favoured by search engines. Wherever possible ensure web addresses are 'human readable' - i.e. they should be easy to read, remember and type. In particular, avoid the use of obscure characters (including the underscore, which is not widely understood by non-technical users, or particularly memorable) and long numerals, e.g. example.com/23857984325. (read more)
- Having mobile optimised HTML is good, but the best way of adapting a website for different screen sizes is to use CSS media queries. (read more)
- Add width and height attributes to all image tags. The width and height you specify should be the same as the source image. If you want to resize an image in the browser, use CSS. (read more)
URL format3.6
4 URLs are less than ideal
- 2 URLs are particularly hard to type or remember.
- Consider URL rewriting as an effective and transparent means of creating appropriate URLs. URLs using unusual characters (such as semi-colons or underscores), long numerals or complex phrasing are very difficult for real people to use or exchange. They also tend to be less favoured by search engines. Wherever possible ensure web addresses are 'human readable' - i.e. they should be easy to read, remember and type. In particular, avoid the use of obscure characters (including the underscore, which is not widely understood by non-technical users, or particularly memorable) and long numerals, e.g. example.com/23857984325.
- 4 URLs are 'dirty'. 'Dirty' URLs include one or more parameters after a question mark (e.g. www.example.com/?pagename=news), instead of a clean URL (e.g. www.example.com/news). Dirty URLs should generally be avoided wherever possible - they are almost impossible for human beings to remember, may expose the technology of the website to hackers and can confuse search engines among other problems. Their use is sometimes necessary for specific applications, and acceptable in small amounts.
- Remove or reduce the number of query parameters in URLs. Consider URL rewriting as an effective and transparent means of creating appropriate URLs.
- 2 URLs include a file extension.
- Avoid use of file extensions wherever possible. File extensions appear at the end of web addresses, and have several negative effects. They make the address harder to remember or type (particularly for non-technical users), and can reveal the underlying technology of the website making it very slightly more vulnerable to hackers. They also tie the implementation of the website to a specific technology, which can make subsequent migration of URLs difficult. Consider URL rewriting as an effective and transparent means of creating appropriate URLs.
Page extensions
- Avoid use of file extensions wherever possible. File extensions appear at the end of web addresses, and have several negative effects. They make the address harder to remember or type (particularly for non-technical users), and can reveal the underlying technology of the website making it very slightly more vulnerable to hackers. They also tie the implementation of the website to a specific technology, which can make subsequent migration of URLs difficult. Consider URL rewriting as an effective and transparent means of creating appropriate URLs.
Mobile8.6
- This website delivers a mobile optimised version of the HTML when accessed on a phone. This is good because visitors on a mobile device will be able to access this website easily.
- Having mobile optimised HTML is good, but the best way of adapting a website for different screen sizes is to use CSS media queries.
Media specific CSS detected
| Media | Min width | Max width | CSS file |
| screen | 1030px | - | 1gr.cz/.../portal.css?rr=1712051591563 |
| all | - | 319px | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 320px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 360px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 375px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 393px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 412px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 480px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 1680px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
Images8.8
59% of images have a clearly defined size
61 images are being resized by the browser
- Some images (41.0%) don't have defined sizes using width and height attributes in the HTML. These attributes are optional, but strongly recommended as they help the browser arrange the page more quickly.
- Add width and height attributes to all image tags. The width and height you specify should be the same as the source image. If you want to resize an image in the browser, use CSS.
Non Explicitly Sized Images
- Add width and height attributes to all image tags. The width and height you specify should be the same as the source image. If you want to resize an image in the browser, use CSS.
- 61 images are being stretched in the browser.
- The width and height you specify in an image tag should be the same as the source image. If you want to resize an image in the browser, use the CSS width and height properties.
Stretched Images
- The width and height you specify in an image tag should be the same as the source image. If you want to resize an image in the browser, use the CSS width and height properties.
Headings9.0
- All pages were found to use defined headings. This is excellent as it allows visitors and search engines to summarise the content of webpages quickly. Correctly defined headings aid accessibility and are particularly important for search engine optimisation.
- Some pages did not define headings correctly. The H1 tag should be used for the most top-level heading, with H2 being used for sub-headings and H3 for further sub-headings and so-on. Not conforming to this convention may confuse visitors.
- Ensure that headings are defined in a semantically correct way, i.e. always start with a H1 tag. This is used to summarise the page content. Further tags (H2, H3, H4 etc) are meant to summarise and partition sections within the content.
Page headings detail
Amount of content9.0
Rendering Chart...
- This website has an average of 711 words per page. The amount of content on a website has been shown to correlate with its search engine ranking.
Amount of content discovered
| Page | Characters | Words |
| absolon.blog.idnes.cz/ | 6907 | 913 |
| absolon.blog.idnes.cz/?strana=2 | 1512 | 184 |
| absolon.blog.idnes.cz/?strana=1 | 6919 | 915 |
| absolon.blog.idnes.cz/blog.aspx?c=479471 | 4969 | 753 |
| absolon.blog.idnes.cz/diskuse.aspx?iddiskuse=A151001_478900_blogidnes | 4989 | 788 |
Server behaviour9.2
404 page
Compression
- This website handles missing pages correctly by sending a 404 HTTP status code.
- This website was served with GZIP encoding. This is very good because it reduces the loading time of a web page.
- This website returns page content with or without a trailing slash on the URLs. Search engines might see these as separate pages with duplicate content which they could penalise for.
- Use a 301 redirect or a canonical meta tag to force search engines to see the correct version.
- This test is not applicable as this website appears to be on a subdomain.
Internal links9.6
- 21 links have no text describing their destination. Links on a page should describe their destination for the benefit of both screen readers and search engine spiders.
- Add meaningful anchor text that describes the link's destination. If the link contains an image, ensure you have provided alt text.
Empty link text
- Add meaningful anchor text that describes the link's destination. If the link contains an image, ensure you have provided alt text.
Analytics10.0
100% of pages use analytics
Google Tag Manager
- Every page in this website is using Google Tag Manager. This is excellent and should allow for a complete analysis of visitor behaviour.
Page titles10.0
100% of pages have defined titles
0% of page titles are weak
- All pages were found to use page titles appropriately. Page titles appear in search results and at the top of the browser's window when visiting the site. Appropriate page titles are particularly important for search engine optimisation.
Meta tags10.0
This is how this website will look in Google search listings:
Amand Absolon - Blog iDNES.cz
absolon.blog.idnes.cz/
Rad se koukam na svet pres hledacek meho fotoaparatu...
- All pages were found to include a meta description. This is good because search engines (like Google) show this text in search result pages.
Meta Tags (name attribute)
Meta Tags (http-equiv attribute)
| Page URL | Name | Content |
| absolon.blog.idnes.cz/ | cache-control | no-cache |
| absolon.blog.idnes.cz/?strana=2 | cache-control | no-cache |
| absolon.blog.idnes.cz/?strana=1 | cache-control | no-cache |
| absolon.blog.idnes.cz/blog.aspx?c=479471 | cache-control | no-cache |
| absolon.blog.idnes.cz/diskuse.aspx?iddiskuse=A151001_478900_blogidnes | cache-control | no-cache |
Pages with no meta description
Printability10.0
100% of pages are optimised for printing
- All of this website appears to be optimised for printing (using CSS).
Media specific CSS detected
| Media | Min width | Max width | CSS file |
| - | - | 1gr.cz/.../layout.css?rr=1712052997755 | |
| - | - | 1gr.cz/.../layout.css?rr=1712052997755 | |
| screen | 1030px | - | 1gr.cz/.../portal.css?rr=1712051591563 |
| - | - | 1gr.cz/.../reklama.css?rr=1710492380665 | |
| - | - | 1gr.cz/.../reklama.css?rr=1710492380665 | |
| all | - | 319px | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 320px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 360px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 375px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 393px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 412px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 480px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| all | 1680px | - | 1gr.cz/.../reklama.css?rr=1710492380665 |
| - | - | 1gr.cz/.../supply.css?rr=1707555947195 |
Freshness10.0
Last updated April 4, 2024
- It looks like this website was last updated on Thursday, 4 April 2024. This is good because visitors perceive up-to-date websites as more credible. Websites that are updated regularly are also spidered by search engines more often.
- To find this information we used the last modified dates reported by this website's server in addition to looking for dates written on each page.
All dates found
Twitteri
This website does not appear to be associated with a Twitter account.
- There was a problem checking the Twitter accounts associated with this website.
Fast, branded website audits
Insites creates professional website reports that can be shared with your clients.
How does Insites compare?
Nibbler | Insites | |
|---|---|---|
| Tests | 17 fixed tests | 50+ testsCovers SEO, SEM, Google My Business, reviews, social media and much more |
| Add your branding | No | Yes |
| Export & share | No | PDF & link |
| Lead generation | No | Embed on your site |
| Competitor audits | No | Yes |
| Test as a batch | No | Yes |
| Integrations + API | No | Yes |
| Multi-lingual | No | 20+ languages |
| Try it free |