bk.com

bk.com · 🇺🇸 United States · Community picks

Not ranked: this scan does not meet the current evidence and freshness requirements.

Scanned

The quick verdict

This sample has no current rank.

Link health

Ranks first

Quality checklist
31.8/100

Breaks ties

Broken links
0

Confirmed in sample

0 links verified · 0 unknown · 1 pages read. Sample only. Unknown links are not counted as broken.

What to fix first

View all priorities →
  1. Meta description

    Add a non-empty meta name="description" that summarizes this page.

  2. Canonical URL

    Declare one valid HTTP(S) canonical URL for each indexable page. It may point to another URL when intentional.

  3. Main heading

    Add a descriptive H1 identifying the main topic.

Fix with your coding assistant

Copy a ready-to-use prompt with the issues and affected URLs.

View full reportConfirmed issues, suggested fixes and the evidence behind them.

The evidence behind this sample

0 confirmed broken links in 0 verified. 0 discovered links could not be verified.

No measurable coverage yet. This score describes the measured sample, not the entire website. Unknown links are not counted as broken.

Broken links
0
Links verified
0
Unverifiable
0

not counted

Pages read
1

0 internal · 0 external

Full standard report · free for everyone. This is a bounded sample, not an audit of every page.

No confirmed broken links in this sample. Unverified URLs are not evidence of healthy links.

Quality checklist

8 passed · 15 need work · 3 not verified. Open a check for the evidence and suggested fix.

SEO
25

Measured performance

107 ms median to homepage response headers. Measurements: 83, 107, 116 ms.

Same crawler, three sequential requests, DNS and TLS included. Lower 100 ms bands win after an equal checklist. This is server/network response, not browser loading or Core Web Vitals.

Static checks inspect crawler-visible HTML; they do not certify accessibility or code quality.

SEO3 to improve
Page titlePassed

1/1 applicable observations passed. 1/1 checklist weight earned.

How to improve: Give each page a descriptive, non-empty <title>.

Distinct page titlesNot applicable

No applicable elements found. Informational; excluded from points.

How to improve: Use a title that describes the purpose of this page rather than repeating the same title across URLs.

Meta descriptionUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Add a non-empty meta name="description" that summarizes this page.

Canonical URLUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Declare one valid HTTP(S) canonical URL for each indexable page. It may point to another URL when intentional.

Root sitemap availableUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Publish a sitemap URL set or index at /sitemap.xml. This checks its root, not every listed URL.

Accessibility0 to improve
Document languagePassed

1/1 applicable observations passed. 1/1 checklist weight earned.

How to improve: Declare a valid language tag on the html element, such as en or pt-BR.

Image alternatives declaredNot applicable

No applicable elements found. Informational; excluded from points.

How to improve: Add alt text to informative images. Use alt="" for decorative images. This check does not judge text quality.

Form controls namedNot applicable

No applicable elements found. Informational; excluded from points.

How to improve: Associate a label with each visible form control, or provide a non-empty aria-label / valid aria-labelledby.

Buttons namedNot applicable

No applicable elements found. Informational; excluded from points.

How to improve: Give every button visible text or an accessible name, including icon-only buttons.

Rendered color contrastNot verified

0/1 applicable observations passed. Informational; excluded from points.

How to improve: Check foreground/background contrast in the rendered page.

Keyboard and focus behaviorNot verified

0/1 applicable observations passed. Informational; excluded from points.

How to improve: Test every interactive control with a keyboard and inspect focus visibility.

Structure3 to improve
Main headingUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Add a descriptive H1 identifying the main topic.

Heading hierarchyUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Nest headings logically without skipping a level, starting with H1.

Main landmarkUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Mark the main content with one <main> or role="main" landmark.

Mobile viewportPassed

1/1 applicable observations passed. 1/1 checklist weight earned.

How to improve: Add meta name="viewport" with width=device-width and do not disable user zoom.

HTTPS pagePassed

1/1 applicable observations passed. 1/1 checklist weight earned.

How to improve: Serve the page over HTTPS with a valid certificate.

No insecure embedded resourcesPassed

1/1 applicable observations passed. 1/1 checklist weight earned.

How to improve: Use HTTPS for embedded script, image, stylesheet, frame, audio and video URLs.

Sharing7 to improve
Open Graph titleUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Provide a non-empty og:title meta property.

Open Graph descriptionUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Provide a non-empty og:description meta property.

Open Graph typeUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Declare og:type, such as website or article.

Open Graph URLUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Set og:url to an absolute HTTP(S) URL for this content.

Open Graph image URLUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Set og:image to an absolute HTTP(S) image URL. Homepage image availability is checked separately.

Open Graph image descriptionNot applicable

No applicable elements found. Informational; excluded from points.

How to improve: Describe the sharing image with og:image:alt.

Social card typeUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Declare twitter:card as summary or summary_large_image for a website card.

Homepage favicon availablePassed

1/1 applicable observations passed. 1/1 checklist weight earned.

How to improve: Serve a non-empty public image with an image Content-Type.

Homepage sharing image availableUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Declare a public image URL for homepage sharing image available.

AI access2 to improve
Content in initial HTMLUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Render meaningful main content on the server so readers can access it without executing JavaScript.

Structured data syntaxUp to +4.5 checklist ptsNeeds work

0/1 applicable observations passed. 0/1 checklist weight earned.

How to improve: Provide JSON-LD with @context and @type (or a typed @graph). Match the markup to the visible content; syntax alone does not validate its meaning.

Performance0 to improve
HTML transfer budgetPassed

1/1 applicable observations passed. 1/1 checklist weight earned.

How to improve: Keep the uncompressed HTML at or below 500 KB. Remove duplicated inline payloads and unnecessary markup.

Repeated homepage HTTP responsePassed

1/1 applicable observations passed. Informational; excluded from points.

How to improve: Improve server response and CDN caching. Median of three requests; 100 ms bands decide the final tiebreak.

  • https://www.bk.com/3/3 successful measurements to response headers. Includes DNS and TLS; excludes rendering.
Browser loading and Core Web VitalsNot verified

0/1 applicable observations passed. Informational; excluded from points.

How to improve: Measure LCP, INP and CLS with browser and field tools.

Checklist quality-v1. Equal weight per applicable scored check, proportional credit across sampled pages. Unverified scored checks earn no points; not-applicable and manual checks are excluded. Full methodology and references.

Page health

From the 1 pages we read. Full details in the report.

Missing titles

0

Duplicate titles

0

Missing descriptions

1

Missing H1

1

Multiple H1

0

Avg response

943 ms

Slowest pages

HTTP response time measured by our crawler; not browser loading speed.

Pages inspected (1)

All 1 pages from this scan.

PageStatusTitleH1ms
https://www.bk.com/200Burger King
Page checklist evidence
  • title: passedBurger King
  • description: failedNo meta description
  • canonical: failedNo canonical URL
  • h1: failed0 H1 element(s)
  • headings: failed0 skipped heading level(s)
  • main: failed0 main landmarks
  • lang: passeden
  • alt: not-applicable0 of 0 images lack an alt attribute
  • labels: not-applicable0 of 0 controls have no HTML label
  • buttons: not-applicable0 of 0 buttons have no HTML name
  • links-named: not-applicable0 of 0 links have no HTML name
  • viewport: passedwidth=device-width, initial-scale=1, shrink-to-fit=no
  • https: passedhttps://www.bk.com/
  • mixed: passed0 HTTP embedded resource URL(s)
  • og-title: failedNo og:title
  • og-description: failedNo og:description
  • og-type: failedNo og:type
  • og-url: failedNo og:url
  • og-image: failedNo og:image
  • og-alt: not-applicableNo sharing image description
  • twitter-card: failedNo social card type
  • readable: failed0 characters of crawler-visible content (minimum 100)
  • jsonld: failed0 of 0 blocks have valid JSON-LD structure
  • html-size: passed3,381 bytes of HTML; budget 500,000
0943

Mobile page report

www.bk.com

https://www.bk.com/

Measured · 9/6/2026, 9:57:25 PM UTC

Speed
34
Accessibility
100
SEO basics
75
Main content (LCP)
41.9 s
Layout shifts (CLS)
0.023
Blocking time (TBT)
5,380 ms

Your next improvements

Measured findings to investigate, ordered by audit score.

1. Total Blocking Time

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. [Learn more about the Total Blocking Time metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-total-blocking-time/).

2. Links do not have descriptive text

Descriptive link text helps search engines understand your content. [Learn how to make links more accessible](https://developer.chrome.com/docs/lighthouse/seo/link-text/).

3. LCP request discovery

[Optimize LCP](https://developer.chrome.com/docs/performance/insights/lcp-discovery) by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

4. Largest Contentful Paint

Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn more about the Largest Contentful Paint metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-largest-contentful-paint/)

5. LCP breakdown

Each [subpart has specific improvement strategies](https://developer.chrome.com/docs/performance/insights/lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.

6. Network dependency tree

[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

7. Document does not have a meta description

Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/).

8. robots.txt is not valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. [Learn more about robots.txt](https://developer.chrome.com/docs/lighthouse/seo/invalid-robots-txt/).

Fix with your coding assistant

Copy a ready-to-use prompt with the issues and affected URLs.

Battle scoring rules

The arena compares five stages: link health, performance, accessibility, SEO, and structure & sharing. Only stages measured with the same method on both sites count. Accessibility and SEO use browser measurements when both have compatible results; otherwise both use the standard checklist. Structure & sharing combines earned and possible checklist points. Most stages won decides the fight, followed by the sum of shared scores and stage order. Identical scores use a deterministic game coin toss. Performance differences up to five points draw. Missing measurements never count as zero. Browser audits do not certify accessibility. The standard scan independently updates ranking when eligible.