AMP Performance Review Service

Why AMP Performance Matters

AMP (Accelerated Mobile Pages) provides performance guarantees through strict constraints. But many AMP implementations fail due to:

• Validation errors — Invalid AMP prevents cache serving
• Poor component usage — Using heavy components when lighter alternatives exist
• Canonical issues — Broken pairing between AMP and canonical pages
• Layout problems — CLS issues from improper sizing

The review ensures your AMP pages are valid, fast, and properly integrated.

What We Analyse

AMP Validation

Invalid AMP pages won’t be served from Google’s cache:

Error Categories

• Prohibited HTML tags and attributes
• Invalid AMP component usage
• CSS size and restrictions (75KB limit)
• Custom JavaScript violations
• Boilerplate requirements

Validation Tools

• AMP Validator results analysis
• Google Search Console AMP report
• Browser extension findings
• Programmatic validation

Component Optimisation

AMP components have performance implications:

Image Handling

• amp-img sizing and layout
• Responsive image implementation
• Lazy loading configuration
• Placeholder strategies

Media Components

• amp-video optimisation
• amp-iframe usage and restrictions
• amp-youtube embedding
• amp-carousel efficiency

Interactive Components

• amp-accordion performance
• amp-lightbox usage
• amp-sidebar implementation
• amp-form optimisation

Core Web Vitals

AMP’s constraints help but don’t guarantee good scores:

LCP Optimisation

• Hero image loading priority
• Above-fold content delivery
• amp-img layout modes
• Preconnect to amp cache

CLS Prevention

• Explicit dimensions on all media
• Reserved space for ads
• Font loading behaviour
• Dynamic content handling

INP Improvement

• AMP runtime efficiency
• Component interaction speed
• Form submission responsiveness
• Carousel/slider performance

AMP-Canonical Pairing

Proper linking is essential for SEO:

Link Validation

• amphtml link from canonical pages
• canonical link from AMP pages
• URL consistency
• Redirect handling

Content Parity

• Content matching requirements
• Structured data consistency
• Metadata alignment
• Image and media matching

Structured Data

Rich results require valid structured data:

Schema Review

• Article/NewsArticle markup
• Product schema for e-commerce
• Recipe markup for food content
• FAQ and HowTo schemas

AMP-Specific Requirements

• Required properties for AMP
• Image specifications
• Publisher/author markup
• Date formatting

Common AMP Issues

Validation Errors

Prohibited Elements

<!-- Invalid: Custom JavaScript -->
<script>console.log('hello')</script>

<!-- Valid: Use amp-bind for interactivity -->
<amp-state id="myState">
  <script type="application/json">{"value": "hello"}</script>
</amp-state>

CSS Violations

• Inline styles exceeding limits
• External stylesheets (not allowed)
• !important overuse
• Prohibited properties

Layout Issues

Missing Dimensions

<!-- Invalid: No dimensions causes layout shift -->
<amp-img src="image.jpg"></amp-img>

<!-- Valid: Explicit dimensions -->
<amp-img src="image.jpg" 
         width="800" 
         height="600" 
         layout="responsive">
</amp-img>

Layout Mode Selection

• responsive: For flexible-width images
• fixed: For exact dimensions
• fill: For container-filling
• intrinsic: For max-width constraints

Performance Problems

Heavy Component Usage

• Multiple amp-iframe instances
• Large amp-carousel galleries
• Excessive amp-ad placements
• Complex amp-animation

Resource Loading

• Too many external requests
• Missing preconnect hints
• Render-blocking resources
• Large custom fonts

AMP Best Practices

Optimised Image Loading

<amp-img 
  src="hero.jpg"
  srcset="hero-400.jpg 400w,
          hero-800.jpg 800w,
          hero-1200.jpg 1200w"
  width="1200"
  height="675"
  layout="responsive"
  alt="Hero image">
  <amp-img fallback
    src="hero-fallback.jpg"
    width="1200"
    height="675"
    layout="responsive"
    alt="Hero image fallback">
  </amp-img>
</amp-img>

Efficient Styling

<style amp-custom>
  /* Keep under 75KB */
  /* Use efficient selectors */
  .article-body p {
    font-size: 18px;
    line-height: 1.6;
  }
  /* Avoid expensive properties */
  /* No !important unless necessary */
</style>

Analytics Implementation

<amp-analytics type="gtag" data-credentials="include">
  <script type="application/json">
  {
    "vars": {
      "gtag_id": "UA-XXXXX-Y",
      "config": {
        "UA-XXXXX-Y": {"groups": "default"}
      }
    }
  }
  </script>
</amp-analytics>

What You’ll Receive

Validation Report

• All validation errors listed
• Error severity and impact
• Specific fix for each error
• Code examples

Performance Analysis

• Core Web Vitals scores
• Component efficiency assessment
• Resource loading waterfall
• Optimisation opportunities

Implementation Guide

• Prioritised fixes
• Code changes needed
• Testing methodology
• Monitoring recommendations

Getting Started

To begin an AMP performance review, provide:

• URLs of AMP pages to review
• Google Search Console access (if available)
• Current validation errors
• Specific AMP concerns
• CMS or framework being used

A quote will be provided within 24-48 hours based on scope.