Earth Notes: On Website Technicals (2020-02)Updated 2020-03-03 20:00 GMT.
I think a few browsers (especially mobile) ignore the
attribute, and unconditionally load the
src URL. If so, these browsers are often going to be old and small and on bad/tight data plans. Hitting them with more image data than they can use is a waste.
As an experiment for lite pages only, I am making the
point to a smaller version of the image where available. I'm leaving everything else intact including the
In some cases an older mobile broswer may then load the smaller image better suited to it. Though an older desktop browser may have to stretch it to fill the dimensions given.
On a modern browser everything should behave as now.
I really don't know how much difference if any that this will make.
2020-02-26: Lazy, Finally
Chrome (plus other Chromium browsers such as Opera) support
loading=lazy, Firefox has it protected behind a flag on the nightly build it seems, and it's apparently on the way for Safari too.
Importantly, the Nu Html Checker will shortly officially allow the attribute, so I will be able to use it at last.
For all body images deep below the fold (well below where I allow ads)
<IMG ...>s will be inserted with
loading=lazy. (This should align reasonably well with the Chrome heuristics for example.) The typically one or two above that will still be
as now to prioritise showing text content.
2020-02-17: Video Captions
An annoyance when trying to edit the captions is that they won't show/play when viewing the page as a file locally, and the long (nominally infinite) cache time via the site front-end prevents even forced reloading. At least in current Firefox, Chrome and Safari.
The solution that I have so far is to freshly open the podcast page in private/stealth mode after each edit.
2020-02-16: Automatic Dark Mode
I'm trying out
I disabled the
blockquote quotes graphic to keep the desktop CSS small enough overall. As it happens this feature wasn't playing that well with dark mode anyway.
2020-02-15: Review Problems
Google has recently started complaining about 'Review' markup, eg in GSC.
In order to try to stamp out some shady self-promotion SEO, it seems, Google now only recognises schema.org/Review in a narrower range of contexts than allowed by schema.org itself.
In particular for EOU that seems only to allow Review for an Event or Product, but since I am not selling anything I cannot complete those properly from GSC's point of view, eg because I have no 'offers' to include in mark-up.
(Though bizarrely Google now seems happy with all my older hReview markup, even where there are multiple instances on a single page.)
This is annoying, and I'm sure I'm not alone with this difficulty.
My markup is meant to be helpful to search engines and others, rather than especially promotional, but seeing errors and warnings in my GSC reports makes me unhappy. Can't GSC understand that it's not all about the money for at least some of us?