Nibbler SEO audit for corp.mobile.rakuten.co.jp
Summary
Overall7.8
The overall score for this website.
Accessibility9.2
How accessible the website is to mobile and disabled users.
The following tests contribute to this score:
Experience7.4
How satisfying the website is likely to be for users.
The following tests contribute to this score:
Marketing4.4
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 12:19 on 14 Apr 2024 (BST).
Top priorities for website improvement
- Consider a leading website analytics solution, such as WebTrends or Google Analytics. (read more)
- Sign up for a Twitter account and make sure it is linked to from your site. (read more)
- 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)
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.
Printability0.0
0% of pages are optimised for printing
- 5 pages of this website do not appear to be optimised for printing (using CSS).
- Add printable stylesheets for all pages, wherever possible. In most cases, websites can share printable stylesheets over many or all pages, as with screen-based stylesheets.
Print optimised pages
Page Print corp.mobile.rakuten.co.jp/ Not detected corp.mobile.rakuten.co.jp/about/?l-id=corp_gnavi_about Not detected corp.mobile.rakuten.co.jp/.../?l-id=corp_gnavi_overview Not detected corp.mobile.rakuten.co.jp/.../?l-id=corp_gnavi_overview-video Not detected corp.mobile.rakuten.co.jp/.../?l-id=corp_gnavi_history Not detected
- Add printable stylesheets for all pages, wherever possible. In most cases, websites can share printable stylesheets over many or all pages, as with screen-based stylesheets.
Media specific CSS detected
URL format3.6
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.
- 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.
Amount of content6.0
Rendering Chart...
- This website has an average of 116 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
Images9.4
28% of images have a clearly defined size
10 images are being resized by the browser
- Most images (72.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.
- 10 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.
Internal links9.4
- 13 links use text that is too long. Links should describe what they link to briefly. Linking a long block of text usually indicates an attempt to trick search engines into ranking those keywords highly (a strategy which does not work). Long linked blocks of text are also harder for people to scan.
- Consider shortening long anchor text.
Overly long link text
- Consider shortening long anchor 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.
Unhandled alternate URLs
- Add a 301 redirect from the other version to the canonical URL.
- This test is not applicable as this website appears to be on a subdomain.
Mobile10.0
- All of this website appears to be optimised for viewing on a mobile phone or a tablet.
Media specific CSS detected
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.
Page titles
| Page title | Notes |
| 楽天モバイル株式会社 | OK |
| 企業情報 | 楽天モバイル株式会社 | OK |
| 会社概要 | 楽天モバイル株式会社 | OK |
| 動画で見る楽天モバイル | 楽天モバイル株式会社 | OK |
| 楽天モバイルの歩み | 楽天モバイル株式会社 | OK |
Headings10.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.
Page headings detail
Meta tags10.0
This is how this website will look in Google search listings:
楽天モバイル株式会社
corp.mobile.rakuten.co.jp/
...
- 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)
Freshness10.0
Last updated February 15, 2024
- It looks like this website was last updated on Thursday, 15 February 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 |
Nibbler tested the following pages
- https://corp.mobile.rakuten.co.jp/
- https://corp.mobile.rakuten.co.jp/about/?l-id=corp_gnavi_about
- https://corp.mobile.rakuten.co.jp/about/overview/?l-id=corp_gnavi_overview
- https://corp.mobile.rakuten.co.jp/about/overview-video/?l-id=corp_gnavi_overview-video
- https://corp.mobile.rakuten.co.jp/about/history/?l-id=corp_gnavi_history