- dotMobi Compliance - Posted by ruadhan 3 years 48 weeks ago
Ready.mobi v2.1.1 is live- You can probably guess by the version number 2.1.1 (from 2.1), there is nothing ground-breaking in this release. Just a few more bug fixes. In particular we have fixed a bug that caused the use of multiple <hr/> tags in your markup to reduce your overall score.
- dotMobi Compliance - Posted by ruadhan 4 years 14 weeks ago
Fixit - Image Resizing- Images such as bitmaps have an intrinsic pixel size. Telling the browser in advance what the size is avoids it having to re-flow the page when it receives it. Resizing images at the server reduces the amount of data transferred and the amount of processing the client has to carry out to scale the image.
- dotMobi Compliance - Posted by ruadhan 4 years 15 weeks ago
- Fixit - Measures
- Avoiding pixel and absolute measures allows the browser to adapt content to fit the display, though there are exceptions to this rule (see below). This test checks for the use of absolulte and pixel measures where relative measures would be more appropriate
- dotMobi Compliance - Posted by ruadhan 4 years 15 weeks ago
- Fixit - Tables
- This test determines if your page uses tables. Tables do not work well on limited size screens and may result in the user having to scroll horizontally to read them. Putting navigational links into tables may result in the user having both to scroll horizontally and vertically to see possible navigational choices.
- dotMobi Compliance - Posted by ruadhan 4 years 15 weeks ago
- Fixit - Tables for layout
- This test attempts to determines if your page is using tables for layout purposes. Tables should be used to present tabular data, rather than to control the layout of a page. The problems associated with using tables for layout are well documented. In particular, they generally require more markup and take longer to render than acheiving the same with CSS.
- dotMobi Compliance - Posted by ruadhan 4 years 16 weeks ago
- Fixit - Nested Tables
- This test determines if your page make use of nested tables. Mobile devices often cannot display nested tables correctly. When a mobile device is capable of displaying nested tables, the computations required to render the tables can consume lot of CPU and add to the display time for the page.
- dotMobi Compliance - Posted by ruadhan 4 years 17 weeks ago
- Fixit - External Resources
- This test determines how many externally linked resources your page relies on. Linked resources include images, stylesheets and other objects. Each externally linked resource requires a separate request across the network. This may add a significant amount to the page load time in the mobile context.
- dotMobi Compliance - Posted by ruadhan 4 years 19 weeks ago
- Fixit - No Frames
- Frames are not supported on many mobile devices, and using them may have unpredictable results. Frames are also considered as being generally problematic. This test checks that your page does not use frames.
- dotMobi Compliance - Posted by ruadhan 4 years 38 weeks ago
- Announcing ready.mobi v2.0
- For those who haven't seen it yet, we've gone live with ready.mobi v2.0 (We were going to call v1.1, but the new features are so cool we figured it was worth bumping up to 2.0). Version 2.0 rocks. New features include
- dotMobi Compliance - Posted by ruadhan 5 years 5 weeks ago
- Fixit - Pop up windows
- Pop-up windows are not supported on many mobile devices, and using them can have unpredicatable results. This test checks that you are not using pop up windows in your markup.
