While the smartphone-optimized pages created on SignalMind look pretty attractive on tablets, our mobile redirect code does not redirect tablet users to the mobile site. Tablet users are typically looking for content available for large screens, and we advise that the large screen version is served to tablet users (unless a separate tablet-optimized version is available, of course).

If you are uploading a PNG or JPEG image for your page header or an image gallery (animated slideshow) and want the image to fill up the width of the page, upload an image 600px wide or wider. Our platform will automatically resize large images to the width of 600px so that they are optimized for size and fit smart phone screens. If you are using a GIF image, however, you would need to resize it yourself first. Note, if you need the image to fill up the width of the mobile page, make it 600px wide.

If you upload an image smaller than 600px, most likely it will not fill the full width of the mobile page (depending on the device screen width and position); however, this may be your desired effect.

Unique visitor is a person who visits a site at least once within the reporting period. Each visitor to the site is only counted once during the reporting period. So if that visitor accesses the site several times, the visitor is counted as one unique visitor in SignalMind mobile website analytics.

A visit is a series of requests from the same visitor in a set period of time. A visit is made up of several hits and page views. Example: if someone visited the site today and yesterday, that would count as 2 visits in our mobile site analytics.

Page view is defined as a view of a page on your site. If a visitor visits 3 pages on the site, that would count as 3 page views. If a visitor reloads the page, this is counted as an additional page view.

You can’t upload a video directly to our platform, but you can embed videos hosted on other platforms (such as Vimeo). Simply copy the video embed code into a Custom HTML widget on your mobile page.

Simply put, W3C mobileOK checker is outdated. It's standards are derived from pre-smartphone days, and do not take into considerations the capabilities of modern phone browsers and much improved connectivity. In addition (and this is according to W3C.org website), “Being mobileOK is neither a guarantee that the Web document may be rendered correctly by all mobile devices, nor an insurance that the user experience was correctly addressed.”

W3C encourages developers “to adapt their content, where appropriate, to exploit the capabilities of the actual device”, and not follow the mobileOK standards too closely. Here is a full blog post on that.