SShortSingh.
Back to feed

Lighthouse en un sitio de 1.382 páginas: qué medir y qué ignorar

0
·5 views

A team measured its 1,382-page static site, built with Astro and hosted on Cloudflare, using Lighthouse 13 against production to check whether new pages lowered scores. Five page templates scored between 98 and 100 in performance, with 100 in accessibility, best practices and SEO, and near-zero layout shift and blocking time. They found that one-to-two-point differences between runs of identical code reflect measurement noise rather than regressions, so repeating the test comes first. Their optimizations included hashing and minifying scripts, which cut one bundle from 106.2 KB to 36.1 KB, and avoiding third-party analytics. The authors also stressed testing one page per template and confirming suspected issues against production, since local environments can produce misleading results.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Google's Android developer verification rules could restrict sideloading on phones within 70 days

A campaign site called Keep Android Open warns that Google is about to tighten control over Android phones. Under new developer verification requirements, apps may need to come from verified developers before they can be installed. Critics argue this would limit users' ability to install software from outside official app stores, a practice known as sideloading. The post gained attention on Hacker News, where it drew a modest discussion. The source material provides only a brief link and summary, so the exact rollout details and timeline remain limited to the campaign's claims.

0
ProgrammingHacker News ·

Shitter: New Nitter Fork Released on Codeberg

A new project called Shitter, described as a fork of the Nitter front-end for Twitter, has been shared on Codeberg. Nitter is an alternative interface that lets users view the platform without JavaScript or an account. The announcement appeared on Hacker News, where it gathered 10 points and 5 comments. The source material provides little detail beyond the project link and discussion metrics, so its specific features and goals are not described here.

0
ProgrammingDEV Community ·

DREX: Brazil's central bank digital currency faces privacy questions

The Central Bank of Brazil is developing DREX, a digital currency built on a permissioned Ethereum-based network called Hyperledger Besu. Unlike decentralized cryptocurrencies, it is run by authorized banks and institutions, with the central bank retaining oversight of the system. Pilot tests revealed that, without extra safeguards, transactions could be visible to network participants, and researchers reportedly exposed balances and transfers during one trial. The bank is evaluating privacy technologies such as zero-knowledge proofs and anonymous transfer protocols, though full privacy is seen as incompatible with anti-money-laundering rules. Implementation is underway, with expansion expected through 2025 and 2026.

0
ProgrammingDEV Community ·

OpenClaw's heartbeat feature: cheap local checks first, LLMs only when needed

OpenClaw, formerly known as Moltbot and Clawdbot, has gained traction for its local automation that monitors a machine, spots drift, and acts early. Its heartbeat feature runs periodic ticks through a layered pipeline, starting with inexpensive deterministic checks such as process status, file state, queue depth, and API health. Model escalation happens only when those checks leave real ambiguity, which reduces cost and unpredictability. The article presents the heartbeat as a control-plane primitive for agent infrastructure, organized as a five-stage loop with strict probe schemas, TTL-based caching, and a health state machine using hysteresis. The guidance is aimed at developers building their own agent systems who want predictable behavior and fewer unnecessary model calls.