Nibbler SEO audit for www.servi.fi
Summary
Overall6.8
The overall score for this website.
Accessibility7.2
How accessible the website is to mobile and disabled users.
The following tests contribute to this score:
Experience6.3
How satisfying the website is likely to be for users.
The following tests contribute to this score:
Marketing3.9
How well marketed, and popular the website is.
The following tests contribute to this score:
Technology7.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 22:53 on 5 Apr 2024 (BST).
Top priorities for website improvement
- Check how the website looks using a mobile and a tablet. Consider adding mobile-only styling using media queries. Some websites employ other techniques for mobile visitors which we cannot currently detect. (read more)
- Consider a leading website analytics solution, such as WebTrends or Google Analytics. (read more)
- Make sure that all the pages of this website include a meta description. If you don't include one, Google will choose a sample of text from the page to appear in the search engine result. By including a meta description, you can control how your search engine result will appear. (read more)
Twitter0.0
This website does not appear to be associated with a Twitter account.
- This website did not contain a link to Twitter.
- Sign up for a Twitter account and make sure it is linked to from your site.
Analytics0.0
0% of pages use analytics
No Analytics Solution
- None of this website is using any recognised analytics software. It is still possible to gather a great deal of information from webserver logs, however complete visitor analysis requires client-side Javascript or an image not found here.
- Consider a leading website analytics solution, such as WebTrends or Google Analytics.
- Note that this test can only detect recognised analytics solutions. If an analytics solution is new, obscure or used in a non-standard way (e.g. it has been customised) it may not be detected.
Meta tags2.0
- All pages include at least some metadata, but no pages have a description meta tag. The description meta data is important as it appears on Google's search result pages.
- Make sure that all the pages of this website include a meta description. If you don't include one, Google will choose a sample of text from the page to appear in the search engine result. By including a meta description, you can control how your search engine result will appear.
Meta Tags (http-equiv attribute)
| Page URL | Name | Content |
| www.servi.fi/ | Content-Type | text/html;charset=utf-8 |
| www.servi.fi/sivu.tmpl?sivu_id=9577 | Content-Type | text/html;charset=utf-8 |
| www.servi.fi/sivu.tmpl?sivu_id=9578 | Content-Type | text/html;charset=utf-8 |
| www.servi.fi/sivu.tmpl?sivu_id=9580 | Content-Type | text/html;charset=utf-8 |
| www.servi.fi/sivu.tmpl?sivu_id=9579 | Content-Type | text/html;charset=utf-8 |
URL format2.0
4 URLs are less than ideal
- 4 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.
- 4 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.
- 80.0% of URLs include an ID query parameter (e.g. www.example.com?sessionid=1234).
- Avoid use of any query parameter ending in id, e.g. 'sessionid;' Google explicitly states that it will not include pages with this format in their index. Consider URL rewriting as an effective and transparent means of creating appropriate URLs.
Mobile3.0
- None of this website appears to be fully optimised for viewing on a mobile or tablet (using CSS media queries). It is important to make sure your content can be viewed easily across a wide range of devices as a growing percentage of web browsing is now done on phones and tablets.
- Check how the website looks using a mobile and a tablet. Consider adding mobile-only styling using media queries. Some websites employ other techniques for mobile visitors which we cannot currently detect.
Device optimised pages
Page Mobile Tablet Viewport www.servi.fi/ Not detected Not detected Not detected www.servi.fi/sivu.tmpl?sivu_id=9577 Not detected Not detected Not detected www.servi.fi/sivu.tmpl?sivu_id=9578 Not detected Not detected Not detected www.servi.fi/sivu.tmpl?sivu_id=9580 Not detected Not detected Not detected www.servi.fi/sivu.tmpl?sivu_id=9579 Not detected Not detected Not detected
- Check how the website looks using a mobile and a tablet. Consider adding mobile-only styling using media queries. Some websites employ other techniques for mobile visitors which we cannot currently detect.
Media specific CSS detected
| Media | Min width | Max width | CSS file |
| screen | - | - | www.servi.fi/.../jquery.ui.autocomplete.css |
| screen | - | - | www.servi.fi/.../styles_embed.css |
Amount of content7.4
Rendering Chart...
- This website has an average of 211 words per page. The amount of content on a website has been shown to correlate with its search engine ranking.
- Consider the amount of text on this website and increase it if appropriate.
Amount of content discovered
| Page | Characters | Words |
| www.servi.fi/ | 2358 | 274 |
| www.servi.fi/sivu.tmpl?sivu_id=9577 | 2875 | 271 |
| www.servi.fi/sivu.tmpl?sivu_id=9578 | 1845 | 174 |
| www.servi.fi/sivu.tmpl?sivu_id=9580 | 2153 | 196 |
| www.servi.fi/sivu.tmpl?sivu_id=9579 | 1422 | 142 |
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
| URL | Heading | Level |
| www.servi.fi/ | Ajankohtaista | H2 |
| www.servi.fi/ | Hopunkallion ravintolan lounashinnat 1.3.2024 alkaen | H2 |
| www.servi.fi/ | Matilda-tuen yhteystiedot | H2 |
| www.servi.fi/ | H3 | |
| www.servi.fi/sivu.tmpl?sivu_id=9577 | Laatupolitiikkamme | H1 |
| www.servi.fi/sivu.tmpl?sivu_id=9578 | Ruokapalvelut | H1 |
| www.servi.fi/sivu.tmpl?sivu_id=9580 | Puhtauspalvelut | H1 |
| www.servi.fi/sivu.tmpl?sivu_id=9579 | Ravitsemusterapeutin palvelut | H1 |
Internal links9.6
- One link has no text describing its 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.
Server behaviour9.7
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.
- Adding or removing a trailing slash to all URLs of this site returns an error page (404). This is OK as no content is being duplicated, but visitors might try browsing to the pages of this website with or without a trailing slash. Ideally, the alternate URL should redirect to the correct page.
- Add a 301 redirect from the other version to the canonical URL.
- This website follows the best practice of using a permanent (HTTP 301) redirect from http://servi.fi to http://www.servi.fi. This is ideal.
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.
Images10.0
0% of images have a clearly defined size
No images are being resized by the browser
- No images have defined sizes.
- 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.
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 |
| - | - | www.servi.fi/tyylit_print_common.css | |
| - | - | www.servi.fi/mallipohja6/tyylit_print.css?_v=2 |
Freshness10.0
Last updated March 4, 2024
- It looks like this website was last updated on Monday, 4 March 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
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 |