How AMP Pages Accelerate Loading in Google
We encountered a situation where a Laravel project with a news section had a high bounce rate on mobile devices. LCP exceeded 4 seconds, and Google was reluctant to rank pages in Top Stories. The solution — developing AMP versions based on Accelerated Mobile Pages (AMP) — an open standard for instant loading. Below is a practical implementation for an article site, based on experience from 10+ projects. We guarantee correct validation and improvement of Core Web Vitals. Our AMP implementation includes creating AMP templates for Laravel, ensuring fast mobile pages and improved Core Web Vitals. AMP implementation pays off through increased CTR and reduced ad costs.
According to official AMP documentation, AMP pages load twice as fast as regular ones and provide TTFB under 0.3 seconds. Reducing bounce rate by 15–20% directly saves contextual advertising budget. Investment in AMP pays off within a few months. For example, one client saved $2,000 per month on Google Ads after implementing AMP. The implementation cost for a typical Laravel site ranges from $1,000 to $2,000, depending on complexity.
AMP Relevance After Rule Changes
After the update of Google's rules, AMP is no longer mandatory for Top Stories, but it remains an effective way to achieve instant loading on slow connections. Google's cache ensures TTFB under 0.3 seconds, and built-in CSS and JS restrictions automatically eliminate issues with CLS and INP. For news and blog sites, this yields CTR growth of up to 20% due to the lightning bolt icon in search results. More details — Accelerated Mobile Pages. A 15–20% increase in CTR boosts conversion and AMP investment payback.
How AMP Improves Core Web Vitals
AMP strictly limits CSS (only inline, up to 75 KB) and forbids blocking scripts, which eliminates content shifts (CLS) and long first content load (LCP). Google's cache further optimizes delivery — TTFB becomes nearly zero. According to our measurements on real projects, LCP decreases from 3.5 to 0.8 seconds (over 4 times faster), and CLS drops from 0.15 to 0.02. Such improvement directly affects mobile search rankings. In fact, AMP pages load 4 times faster than regular pages on 3G networks, as shown in the comparison table below.
Structure of an AMP Document
<!doctype html>
<html ⚡ lang="ru">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1">
<!-- AMP boilerplate -->
<style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;}</style>
<noscript><style amp-boilerplate>body{-webkit-animation:none}</style></noscript>
<!-- AMP runtime -->
<script async src="https://cdn.ampproject.org/v0.js"></script>
<!-- Canonical link to the regular page -->
<link rel="canonical" href="https://www.amp.dev/articles/{{ $article->slug }}">
<!-- Custom styles (only inline, max 75KB) -->
<style amp-custom>
body { font-family: sans-serif; margin: 0; }
.article { max-width: 680px; margin: 0 auto; padding: 16px; }
h1 { font-size: 1.75rem; line-height: 1.3; }
p { line-height: 1.7; color: #374151; }
</style>
<title>{{ $article->title }}</title>
</head>
<body>
<article class="article">
<h1>{{ $article->title }}</h1>
<!-- AMP image with explicit dimensions and relevant alt -->
<amp-img src="{{ $article->cover_url }}"
width="1200" height="630"
layout="responsive"
alt="Example AMP image for fast page loading">
</amp-img>
<div>{{ $article->content_amp }}</div>
</article>
<!-- AMP Analytics -->
<amp-analytics type="gtag" data-credentials="include">
<script type="application/json">
{
"vars": { "gtag_id": "G-XXXXXXXX" },
"triggers": { "trackPageview": { "on": "visible", "request": "pageview" } }
}
</script>
</amp-analytics>
</body>
</html>
How to Implement AMP on Laravel?
Implementing AMP templates on Laravel involves several steps:
- Creating a controller to generate AMP versions. In it, convert HTML content to AMP-compatible: replace
<img>with<amp-img>, remove scripts and inline styles. - Writing a converter — a function that parses HTML and replaces forbidden elements. All images must have explicit width and height, otherwise the AMP validator will throw an error.
- Configuring routes and adding
link[rel=amphtml]on the regular page. - Validating all AMP pages using
amphtml-validator.
// AmpController
class AmpController extends Controller
{
public function article(Article $article): View
{
$ampContent = $this->convertToAmp($article->content);
return view('amp.article', [
'article' => $article,
'amp_content'=> $ampContent,
]);
}
private function convertToAmp(string $html): string
{
// img → amp-img
$html = preg_replace_callback(
'/<img([^>]*)>/i',
function ($matches) {
$attrs = $matches[1];
preg_match('/width=["\']?(\d+)["\']?/i', $attrs, $w);
preg_match('/height=["\']?(\d+)["\']?/i', $attrs, $h);
$width = $w[1] ?? 1200;
$height = $h[1] ?? 630;
return "<amp-img{$attrs} width=\"{$width}\" height=\"{$height}\" layout=\"responsive\"></amp-img>";
},
$html
);
$html = preg_replace('/<script\b[^>]*>(.*?)<\/script>/is', '', $html);
$html = preg_replace('/\s*style\s*=\s*["\'][^"\']*["\']/i', '', $html);
$html = preg_replace('/\s*onclick\s*=\s*["\'][^"\']*["\']/i', '', $html);
return $html;
}
}
Routing and Canonical Link
// routes/web.php
Route::get('/amp/articles/{article:slug}', [AmpController::class, 'article'])->name('amp.article');
// On the regular page — link[rel=amphtml]
// In <head>:
<link rel="amphtml" href="{{ route('amp.article', $article) }}">
AMP Validation: Common Errors
Even experienced developers make mistakes: forgetting to specify dimensions for <amp-img>, using external CSS, or inserting <script> tags. For automated checking, we use the AMP Validator CLI or browser extension. Example command:
npm install -g amphtml-validator
amphtml-validator https://www.amp.dev/amp/articles/my-article
amphtml-validator ./public/amp/test.html
You can also integrate validation into CI/CD: run a script checking all AMP pages after each deployment. This is especially important if content is updated frequently.
Common validation errors in AMP
| Error | Cause | Solution |
|---|---|---|
| Missing image dimensions | Missing width/height for amp-img | Always specify actual dimensions |
| External CSS | Loading external .css file | Move styles to |