Jens Oliver Meiert

Performance

5 Ways to Reduce HTML File Size on Your Website, Step 0

The journey begins with an unpopular step.

#14 · · ,

An HTML Optimizer’s Config for html-minifier

Jad Joubran asked me about my configuration for html-minifier the other week, and in a hurry I pointed him to the config I had worked out for sum.cumo. In my own projects, however, I work with a different, more ambitious setup.

#13 · ·

Optional HTML: Everything You Need to Know

Optional HTML can be left out to improve performance, to guide code comprehension, and to hone the craft. An overview over all optional tags, rules around quotes for attribute values, and omissible attribute value defaults, as well as notes on pitfalls and tools.

#12 · ·

Image Compression: How to Super-Easily Set Up Automated Base Optimization

Setting up image compression tooling is easy—and for those who want to err on the safe side automatically employing lossless compression, it’s even easier with a solution from sum.cumo: Merlin.

#11 · ·

Understanding Image Compression: Tooling and Context

Image compression plays an important role in performance optimization. It seems straightforward but is a little deceptive, however, because it consists not of one but two parts—and it’s usually lack of understanding of one part that causes problems.

#10 · ·

HTML and Performance: Leave Out Optional Tags and Quotes

As experts we should know what code is optional and leave it out, and our production systems should do a better job assisting us with that. After all the years of neglecting basic HTML optimization, let’s think about taking the next step and not ship optional HTML markup.

#9 · · ,

On Visions for Performance, or: Performance Optimization Is a Process

It’s smart to have a vision for what one wishes to achieve for the performance of a site or app. Yet even the soundest approaches to performance visions have their problems, and in them we recognize that performance, or performance optimization, is indeed a process.

#8 · ·

Performance Rule #1: Do What You Need to Do—But Not More

Web Performance has over the age of the Web not only turned into a discipline by itself, but also a complex one at that. While important much less so for revenue but for user experience and accessibility reasons, there’s a particular angle at performance that makes the matter very simple: the pragmatic angle.

#7 · ·

Performance of CSS Selectors Is Still Irrelevant

From my upcoming book on CSS optimization: Selector performance is not something to optimize for as the price we pay for it is terrible: We micro-manage our work for gains that aren’t noticeable.

#6 · ·

Let’s Make The Web Faster

Two weeks after my last outcry regarding slowness on the Web there’s a more proactive response: Google launched code.google.com/speed, subtitled “let’s make the Web faster.”

#5 · ·

Performance of CSS Selectors Is Irrelevant

…if you like to have a strict read of Steve Souders’ recent research. We’ve still got few but now a few more numbers backing up what we always suspected, that merely optimizing selectors is micro-optimization.

#4 · ·

Performance and RFC 2396

RFC 2396 specifies that relative URIs like //foo get resolved as http://foo. This means, if you link a resource like https://example.com/, @ href may as well just point to //example.com/.

#3 · ·

CSS: Simple Rules for Better Organization and More Efficiency

“Organization is not everything, but without organization, everything is nothing,” one of my teachers used to say. Almost everything benefits from organization, and so does work with CSS—especially when working with many people.

#2 · · ,

Load Time, the UX Factor: Facts and Measures

Load time of websites seems to remain our industry’s stepchild, but the vision is real-time surfing, not spending bandwidth improvements. There are still some facts and measures to consider when it comes to fast websites with a certain ease of use. Here are eight, to be exact.

#1 · ·