Remove Hardware Remove Internet Remove Servers Remove Website Performance
article thumbnail

How Improving Website Performance Can Help Save The Planet

Smashing Magazine

How Improving Website Performance Can Help Save The Planet. How Improving Website Performance Can Help Save The Planet. You may not think about it often, but the Internet uses a colossal amount of electricity. Generally speaking, we can also run the top command on any server to which we have shell access.

article thumbnail

The Great Firewall of China: Obstacles to Monitoring Performance

Dotcom-Montior

The entire country of China’s internet connectivity is shielded by the Great Firewall (GFW). There are three state-owned ISP providers, China Unicom, China Telecom, and China Mobile , that control internet in China. The most recent technology automatically shuts internet off whenever blacklisted URLs are accessed.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Reducing Carbon Emissions On The Web

Smashing Magazine

The only time the Internet was mentioned was as a tool for communicating with one another without the need to chop down more trees, or for working without a commute. So, when people first started talking about the Internet having similar carbon emissions to the airline industry , I was a bit skeptical. More after jump!

Website 136
article thumbnail

Front-End Performance Checklist 2020 [PDF, Apple Pages, MS Word]

Smashing Magazine

Is it worth exploring tree-shaking, scope hoisting, code-splitting, and all the fancy loading patterns with intersection observer, server push, clients hints, HTTP/2, service workers and — oh my — edge workers? It used to provide an insight into how quickly the server outputs any data. What does it mean? Image source ).

article thumbnail

Front-End Performance Checklist 2019 [PDF, Apple Pages, MS Word]

Smashing Magazine

Is it worth exploring tree-shaking, scope hoisting, code-splitting, and all the fancy loading patterns with intersection observer, server push, clients hints, HTTP/2, service workers and — oh my — edge workers? Long FMP usually indicates JavaScript blocking the main thread, but could be related to back-end/server issues as well.

article thumbnail

Front-End Performance Checklist 2021

Smashing Magazine

So, if we created an overview of all the things we have to keep in mind when improving performance — from the very start of the project until the final release of the website — what would that look like? It used to provide an insight into how quickly the server outputs any data. What does it mean?