Practical guides on the things our tools actually do — which image format to pick, why a PDF is huge, what makes a password hard to crack. Written to explain, not to fill a page.
Without Open Graph tags, every platform guesses what your page is about — and they guess badly, cache the guess, and give you no obvious way to correct it.
Read the guideIt exists to move binary data through channels that only accept text. It is not compression, it is not security, and it makes everything about a third bigger.
Read the guideEvery service has a different ceiling — 25 MB, 16 MB, 100 MB — and hitting it is not guesswork. Work backwards from the limit and the settings choose themselves.
Read the guidePerformance advice is usually a list of forty things. In practice four causes account for almost every slow page, and they have a natural order of investigation.
Read the guideOne rewrites your code smaller; the other squeezes the bytes in transit. They stack — but the second does far more of the work than most people assume.
Read the guideThe television version of "enhance" is a lie, but modern upscaling is not. The distinction is exactly what the model is putting back — and it is not the detail you lost.
Read the guideThere are around sixty. About ten decide whether your site works and whether it stays in the index — including one that is technically fine and quietly the worst outcome of all.
Read the guideOver one year the difference is rounding. Over thirty it is several times your money — and the same mechanism works against you on a credit card balance.
Read the guideSchema.org has hundreds of types and Google acts on a couple of dozen. Adding the rest is markup nobody reads. Here is which ones change what appears in a search result.
Read the guidePeak level and perceived loudness are different measurements, and every streaming platform now normalises on the second one. Turning everything up stopped working around 2015.
Read the guideJSON has a deliberately tiny specification, which means there is a short and finite list of ways to break it. The error message rarely points at the right character.
Read the guideIt is not edge detection and it is not magic. It is a neural network guessing a transparency value for every single pixel — which explains exactly where these tools succeed and where they fall apart.
Read the guideIt controls crawling, not indexing. The distinction sounds pedantic until you realise it is why a page you blocked still shows up in Google — and why blocking it made that impossible to fix.
Read the guideA JWT is signed, not hidden. Anyone holding one can read every claim inside it — which is fine, expected, and the source of the most common mistake people make with them.
Read the guideOne redirect is fine. Four in a row is a page that takes an extra second to open and a crawler that may give up before it arrives. They accumulate silently over years of site changes.
Read the guideEvery property that makes a hash function good at checksums makes it bad at passwords. Bcrypt and Argon2 are deliberately, expensively slow, and that is the entire feature.
Read the guideNewer codecs are genuinely smaller at the same quality. They are also slower to encode and, in one case, quietly unplayable on hardware people still own. Here is the trade in plain terms.
Read the guideA canonical tag says "index this URL, not the one you are on". It is a hint, not an order — and the most common mistakes make an entire site invisible without anything appearing to be wrong.
Read the guideThe monthly payment is one formula. What it hides is that the early years of a long loan are almost entirely interest — which is why an extra payment in year two is worth several in year twenty.
Read the guideThey get used interchangeably in conversation and they are not remotely interchangeable in practice. Confusing two of them is behind a large share of real security failures.
Read the guideMP3 is thirty years old and still the safe answer. That is a statement about compatibility, not quality — and for three of the four common jobs, something else is clearly better.
Read the guideIt is not a ranking factor and has not been one since 2009. It is still one of the highest-leverage 155 characters on your site, for a completely different reason.
Read the guideResolution gets the blame and bitrate does the damage. Understanding which of the two you are actually changing is the difference between a smaller file and a ruined one.
Read the guideThe numbers, plus the two concepts — aspect ratio and safe area — that let you work them out yourself when a platform changes them next month.
Read the guidePercent-encoding exists because a URL can only legally contain a small set of characters. Understanding which ones — and why — makes a whole category of broken links obvious.
Read the guideThe quality slider is not a percentage of anything. Here is what lossy compression really discards, why it looks fine at 80 and terrible at 40, and why some images break far sooner.
Read the guideMost password advice optimises for the wrong thing. The maths of guessing says length beats complexity, and the substitutions everyone makes buy almost nothing.
Read the guideA PDF is a container, and almost all of its weight is usually one thing. Find which one, and the fix is obvious — and it is rarely "compress harder".
Read the guideFour formats, four different jobs. The rule is simpler than the arguments about it suggest — and picking wrong costs you either file size or visible quality.
Read the guideGet the latest tools, AI features, and product updates. No spam.