What your site is actually doing.

Audit of https://www.apple.com/, run August 7, 2026. 13 issues were found. I want them fixed.

## Context
- Site: https://www.apple.com/
- Mobile LCP (lab median): 254 ms
- Desktop LCP (lab median): 254 ms
- Page weight (median): 4.5 MB
- Tap targets under 44px: 11% (18 of 164)
- Evidence base: 4 mobile + 2 desktop loads + Google CrUX field data

## Already working, do not change these
- Speed is good: Real Chrome visitors see the main content in 1.6s (Google's "good" bar is 2.5s). This is field data from actual users, not a lab guess.
- Layout stays put as it loads: Real visitors see only 0.01 of layout shift (good is under 0.10), so the page is not jumping under their finger.
- No JavaScript errors on load: Nothing threw a script error across the test loads, so buttons and tracking are not silently breaking mid-session.
- Search basics are in place: Lighthouse scores SEO 92/100. The fundamentals Google looks for are present.
- Accessible to most visitors: Lighthouse accessibility is 92/100, so screen-reader and contrast basics are largely handled.
- Layout holds on phone and desktop: Nothing spilled past the edge at either 390px (phone) or 1366px (desktop), so the structure is responsive.

## Issues, most damaging first

### 1. [HIGH] Broken internal links
Category: SEO, Conversion
Why it matters: 1 internal link target returned an error (404/410/5xx) or did not respond. Broken links waste crawl budget, frustrate visitors, and leak ranking signal. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)
Exact examples found: https://www.apple.com/us/shop/goto/account (no response)

### 2. [MEDIUM] Page is heavy and slow on mobile data
Category: Performance
Why it matters: Each visit downloads about 4.5 megabytes, roughly 1057 KB of images and 244 KB of JavaScript across 52 separate downloads. On a fast connection that's fine. On a phone with patchy mobile data, that's several seconds of blank screen before the page is readable.
How we know: median across loads

### 3. [MEDIUM] 9 interactive elements have no stable, accessible identity
Category: Accessibility (WCAG), Tracking
Why it matters: These elements are clicked like buttons but expose no accessible name, or are a plain div/span used as a control with no role. Assistive tech announces only a role (or nothing), and analytics and heatmaps have no human-readable label or stable selector to bind the click to, so the click is both inaccessible and untrackable, and any redesign silently breaks click aggregation. Give each one a real <button>/<a>, an aria-label, and a stable id or data-attribute.
Exact elements found: (a.tile-link) (no accessible name), (a.tile-link) (no accessible name), (a.tile-link) (no accessible name), (a.tile-link) (no accessible name), (a.tile-link) (no accessible name), (a.tile-link) (no accessible name), (a.tile-link) (no accessible name), (a.tile-link) (no accessible name)

### 4. [MEDIUM] Expose a last-updated date (freshness)
Category: AI Search, SEO
Why it matters: ChatGPT cites recently-updated pages roughly 76% of the time and passes over stale, undated ones. These pages expose no machine-readable dateModified. Refresh the content and add dateModified (Article schema / meta). (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)

### 5. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 50 of 50 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0.01, which is fine), most likely because space is reserved another way (CSS), so this is not causing visible jumps today. It is still worth setting explicit dimensions or a CSS aspect-ratio so a slow connection or a future style change cannot reintroduce shift.
Exact elements found: hero_iphone_family__be5jkzxszb1e_large.jpg "iPhone 17 Pro, back exte", hero_back_to_school_startframe__cd4vg5frm39e_large.png, hero_back_to_school_2026__cz07tzsg14sy_large.jpg "Students carrying variou", hero_macbook_air_m5__eb1idggd120y_large.jpg "Two open MacBook Air lap", promo_logo_ipad_air__dqdj4ni03quu_large.png, promo_ipad_air_m4__bgcv7t286k8y_large.jpg "iPad Air models floating"

### 6. [LOW] Search-result title is leaving room on the table
Category: SEO
Why it matters: Google gives you about 60 characters of headline space in search results. This page is using 5. Adding the value proposition or a relevant keyword gives someone one more reason to click.

### 7. [LOW] Security headers are missing or weak
Category: Security
Why it matters: The server response is missing browser-hardening headers that protect visitors and are a standard security and agency checklist item. Missing or weak here: a modern Referrer-Policy (the current one leaks full URLs to other sites). These are set at the server, CDN, or host level (most platforms expose them in settings or a config file) and do not change how the site looks or performs.

### 8. [LOW] 8 generic CTA links/buttons ("Click here", "Learn more", "Submit")
Category: Accessibility (WCAG), Conversion
Why it matters: Screen-reader users hear a list of "click here, click here, learn more" with no context. Sighted users learn nothing about where the link goes from the label alone. Rewrite each CTA to describe the destination ("See pricing", "Read the case study").
Exact elements found: "Learn more" (a), "Learn more" (a), "Learn more" (a), "Learn more" (a), "Learn more" (a)

### 9. [LOW] No third-party analytics tag detected
Category: Tracking
Why it matters: No Google Analytics, GA4, or other third-party analytics tag was found in the page. If you rely only on platform or server-side analytics that is fine; but if not, a third-party tag is the baseline way to see how many visitors arrive, where they come from, and what converts. First-party or server-side analytics are not detectable from the outside, so this may already be handled.

### 10. [LOW] No email capture or newsletter detected
Category: Conversion
Why it matters: No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. If capturing visitors is relevant to this site, an email signup builds an owned audience you keep regardless of ad costs. Not every site needs one.

### 11. [LOW] Unused JavaScript is being downloaded
Category: Performance
Why it matters: Code that never runs on this page still costs download and parse time on every visit. Splitting or removing it speeds up load. Lighthouse measured: Est savings of 152 KiB.

### 12. [LOW] Unused CSS is being downloaded
Category: Performance
Why it matters: Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 39 KiB.

### 13. [LOW] No llms.txt file
Category: SEO
Why it matters: No /llms.txt. This emerging standard gives AI search engines a clean, structured map of your most important content, improving how they understand and cite your site.

## How to respond
Work through the issues in order. For each one give me the specific change that fixes it: real code or real copy, not advice. Keep changes minimal and match the existing style of the site.
Where several issues share one root cause, say so and fix it once rather than patching each symptom.
If an issue cannot be fixed without seeing more of the code, say exactly which file or selector you need instead of guessing.

{
  "generated_by": "Harvv",
  "report_url": "https://www.apple.com/",
  "generated_at": "2026-08-21T19:25:53.032Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": true,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 254,
    "desktop_lcp_ms": 254,
    "mobile_ttfb_ms": 31,
    "mobile_fcp_ms": 120,
    "page_weight_kb": 4619
  },
  "finding_count": 13,
  "findings": [
    {
      "severity": "high",
      "title": "Broken internal links",
      "detail": "1 internal link target returned an error (404/410/5xx) or did not respond. Broken links waste crawl budget, frustrate visitors, and leak ranking signal. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)",
      "device": "both",
      "tags": [
        "SEO",
        "Conversion"
      ],
      "topic": "broken_internal_links",
      "confidence": "measured",
      "evidence": [
        "https://www.apple.com/us/shop/goto/account (no response)"
      ]
    },
    {
      "severity": "medium",
      "title": "Page is heavy and slow on mobile data",
      "detail": "Each visit downloads about 4.5 megabytes, roughly 1057 KB of images and 244 KB of JavaScript across 52 separate downloads. On a fast connection that's fine. On a phone with patchy mobile data, that's several seconds of blank screen before the page is readable.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "page_weight",
      "confidence": "sampled",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "9 interactive elements have no stable, accessible identity",
      "detail": "These elements are clicked like buttons but expose no accessible name, or are a plain div/span used as a control with no role. Assistive tech announces only a role (or nothing), and analytics and heatmaps have no human-readable label or stable selector to bind the click to, so the click is both inaccessible and untrackable, and any redesign silently breaks click aggregation. Give each one a real <button>/<a>, an aria-label, and a stable id or data-attribute.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Tracking"
      ],
      "topic": "untrackable_elements",
      "confidence": "measured",
      "evidence": [
        "(a.tile-link) (no accessible name)",
        "(a.tile-link) (no accessible name)",
        "(a.tile-link) (no accessible name)",
        "(a.tile-link) (no accessible name)",
        "(a.tile-link) (no accessible name)",
        "(a.tile-link) (no accessible name)",
        "(a.tile-link) (no accessible name)",
        "(a.tile-link) (no accessible name)"
      ]
    },
    {
      "severity": "medium",
      "title": "Expose a last-updated date (freshness)",
      "detail": "ChatGPT cites recently-updated pages roughly 76% of the time and passes over stale, undated ones. These pages expose no machine-readable dateModified. Refresh the content and add dateModified (Article schema / meta). (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)",
      "device": "both",
      "tags": [
        "AI Search",
        "SEO"
      ],
      "topic": "geo",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "50 of 50 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0.01, which is fine), most likely because space is reserved another way (CSS), so this is not causing visible jumps today. It is still worth setting explicit dimensions or a CSS aspect-ratio so a slow connection or a future style change cannot reintroduce shift.",
      "device": "both",
      "tags": [
        "Performance",
        "SEO"
      ],
      "topic": "image_dims",
      "confidence": "measured",
      "evidence": [
        "hero_iphone_family__be5jkzxszb1e_large.jpg \"iPhone 17 Pro, back exte\"",
        "hero_back_to_school_startframe__cd4vg5frm39e_large.png",
        "hero_back_to_school_2026__cz07tzsg14sy_large.jpg \"Students carrying variou\"",
        "hero_macbook_air_m5__eb1idggd120y_large.jpg \"Two open MacBook Air lap\"",
        "promo_logo_ipad_air__dqdj4ni03quu_large.png",
        "promo_ipad_air_m4__bgcv7t286k8y_large.jpg \"iPad Air models floating\""
      ]
    },
    {
      "severity": "low",
      "title": "Search-result title is leaving room on the table",
      "detail": "Google gives you about 60 characters of headline space in search results. This page is using 5. Adding the value proposition or a relevant keyword gives someone one more reason to click.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "title",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Security headers are missing or weak",
      "detail": "The server response is missing browser-hardening headers that protect visitors and are a standard security and agency checklist item. Missing or weak here: a modern Referrer-Policy (the current one leaks full URLs to other sites). These are set at the server, CDN, or host level (most platforms expose them in settings or a config file) and do not change how the site looks or performs.",
      "device": "both",
      "tags": [
        "Security"
      ],
      "topic": "security_headers",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "8 generic CTA links/buttons (\"Click here\", \"Learn more\", \"Submit\")",
      "detail": "Screen-reader users hear a list of \"click here, click here, learn more\" with no context. Sighted users learn nothing about where the link goes from the label alone. Rewrite each CTA to describe the destination (\"See pricing\", \"Read the case study\").",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "link_text",
      "confidence": "measured",
      "evidence": [
        "\"Learn more\" (a)",
        "\"Learn more\" (a)",
        "\"Learn more\" (a)",
        "\"Learn more\" (a)",
        "\"Learn more\" (a)"
      ]
    },
    {
      "severity": "low",
      "title": "No third-party analytics tag detected",
      "detail": "No Google Analytics, GA4, or other third-party analytics tag was found in the page. If you rely only on platform or server-side analytics that is fine; but if not, a third-party tag is the baseline way to see how many visitors arrive, where they come from, and what converts. First-party or server-side analytics are not detectable from the outside, so this may already be handled.",
      "device": "both",
      "tags": [
        "Tracking"
      ],
      "topic": "no_analytics",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No email capture or newsletter detected",
      "detail": "No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. If capturing visitors is relevant to this site, an email signup builds an owned audience you keep regardless of ad costs. Not every site needs one.",
      "device": "both",
      "tags": [
        "Conversion"
      ],
      "topic": "no_email_capture",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Unused JavaScript is being downloaded",
      "detail": "Code that never runs on this page still costs download and parse time on every visit. Splitting or removing it speeds up load. Lighthouse measured: Est savings of 152 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_js",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Unused CSS is being downloaded",
      "detail": "Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 39 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No llms.txt file",
      "detail": "No /llms.txt. This emerging standard gives AI search engines a clean, structured map of your most important content, improving how they understand and cite your site.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "missing_llms_txt",
      "confidence": "measured",
      "evidence": []
    }
  ]
}