Developer and semantic SEO practitioner
Developer · Machine learning and deep learning · Semantic SEO
I build software, and I work at the intersection of two things that turn out to be closely related: machine learning, and how search engines actually understand a page.
My background is in development and in machine learning and deep learning — the practical end of it, where a model has to run somewhere and produce something a person can rely on. That is the same instinct behind the tools here: the compression on this site runs in your browser, using the encoders the browser already has, because that is the honest way to do the job without asking anyone to hand over their files.
The other half of my work is semantic SEO. Not keyword density, but topical structure — how a subject decomposes into entities and attributes, how pages relate to one another, and how a site demonstrates that it actually covers a field rather than gesturing at it. That is why this site has a specification table on every tool page, why the FAQ answers are in the initial HTML, and why several pages state plainly what these tools cannot do.
I wrote the guides on this site myself. Where something is a rule of thumb rather than a measured fact, it says so.
Quality 80 is not 80% of anything. It is an index into a quantisation table. Measured on one photograph: dropping from 100 to 90 removes 77% of the file and 4.2 dB of fidelity; dropping from 40 to 30 removes 17% and costs almost as much.
8 min read
Resize before you compress. Measured on one photograph: half the width at quality 80 produced a 16.4 KB file, while full width at quality 40 produced 20.6 KB and looked far worse. The order of operations matters more than the settings.
8 min read
WebP produced a 27.0 KB file against MozJPEG's 41.1 KB on the same photograph at slightly higher measured fidelity — 34% smaller. It also produced a larger file than JPEG on random noise. The advantage is real and content-dependent.
9 min read
PNG stored the same photograph in 1274.1 KB where JPEG needed 67.5 KB — nineteen times larger. On a flat graphic PNG won. On a smooth gradient PNG lost to JPEG by a factor of two, which surprises most people.
9 min read
A photograph from a phone can carry the coordinates of the place it was taken, the camera serial number and the exact timestamp. Removing that data is straightforward. Removing it carelessly rotates your photos sideways.
9 min read
Attachments are base64-encoded in transit, which inflates them by about a third. A 20 MB limit is really a 15 MB limit. Resize to 1600 pixels on the long edge and encode at quality 80, and a photograph lands near 150 KB.
9 min read