Skip to content
Audit Complete

Results for https://valvesoftware.com

Visit site
Singapore Singapore · Singapore Completed: Apr 22, 2026 23:35 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
D69

Site Health

Score: 69 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Major barriers for users with disabilities — up to 15% of your audience.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

jQuery · 1759 peers
You 69
·
Avg 73
At average
0 50 100
Better than 7% of jQuery sites See full jQuery benchmark →
Microsoft · 2328 peers
You 69
·
Avg 72
At average
0 50 100
Better than 9% of Microsoft sites See full Microsoft benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

Page weighs 4.6 MB (4.0 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

2 image(s) missing alt attribute

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fvalvesoftware.com)](https://beavercheck.com/results/566debeb-99cd-47d9-8aec-25b9e0540fc5)
<a href="https://beavercheck.com/results/566debeb-99cd-47d9-8aec-25b9e0540fc5"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fvalvesoftware.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fvalvesoftware.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 5.8s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 5.8s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Conversion Barriers

1 critical 5 warning

6 barrier(s) likely increasing bounce by ~23%.

Speed (1)

Page takes 5.8s to load

+12% bounce

Users abandon at ~3s — you're 3.3s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (2)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€425 investment → €3,594/month returns + EUR 120,500,000 risk avoided

Payback period: < 1 month First-year ROI: +10047%

Investment

€425

5h · 5 findings

Monthly returns

€3,594 /mo

~€43,126 / year

  • Conversions recovered €3,593
  • Bandwidth savings €0.94

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

Payback period

0 12mo 24mo

€128 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€425

5.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€128 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,668 / month at risk

~€120,500,011 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 10,000 – EUR 20,000,000

+8 more

Bandwidth Waste

€0.94 /mo

12647.9 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~1.3 MB per page load
    Saves €0.94/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

70
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
68
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.91 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.83 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

114 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.012

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.41 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

6.64 s

Detailed Report

Audit breakdown by category with detailed findings.

70

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:2.519 source:map[column:9837 line:2 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:38.202 source:map[type:text value:[unattributed]]] map[reflowTime:0.646 source:map[column:21731 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]] map[reflowTime:0.288 source:map[column:21828 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]] map[reflowTime:0.227 source:map[column:22058 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]] map[reflowTime:0.142 source:map[column:22485 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]] map[reflowTime:0.998 source:map[column:22640 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]] map[reflowTime:0.218 source:map[column:22785 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]]]

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.valvesoftware.com/en/http/1.1
www.valvesoftware.com/public/css/global.css?v=lmcEcZ-F-ilx&_cdn=akamaihttp/1.1
www.valvesoftware.com/public/css/fonts.css?v=xSaYcfyOLADT&_cdn=akamaihttp/1.1
www.valvesoftware.com/public/css/forms.css?v=50QYppCbB4ar&_cdn=akamaihttp/1.1
www.valvesoftware.com/public/css/jobs.css?v=Gwqg1pBmxEi2&_cdn=akamaihttp/1.1
/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5z...http/1.1
/en/public/javascript/valvesoftware.js?v=Yw_MCZWiaUD0&_cd...http/1.1
www.valvesoftware.com/en/public/javascript/jobs.js?v=KKAPM5KmPVH7&_cdn=akamaihttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_fullsize.jpghttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_fullsize.jpghttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_fullsize.jpghttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/steam_logo_footer.pnghttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/steamworks_logo_footer.pnghttp/1.1
www.valvesoftware.com/public/css/fonts/apercu-medium.WOFFhttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/search.pnghttp/1.1
www.valvesoftware.com/public/css/fonts/apercu-black.WOFFhttp/1.1
www.valvesoftware.com/public/css/fonts/apercu-regular.WOFFhttp/1.1
www.valvesoftware.com/public/css/fonts/apercu-bold.WOFFhttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_fullsize.webmhttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_fullsize.webmhttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_fullsize.webmhttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/favicon.icohttp/1.1

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.7 s

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 1.2 s 242.2 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.col_3 > div.steamworks_logo > a > img div.col_3 > div.steamworks_logo > a > img
cdn.akamai.steamstatic.com/valvesoftware/images/steamworks_logo_footer.png
div.col_3 > div.steam_logo > a > img div.col_3 > div.steam_logo > a > img
cdn.akamai.steamstatic.com/valvesoftware/images/steam_logo_footer.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
Improve image delivery
LCP breakdown
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
JavaScript execution time 0.4 s
Minimizes main-thread work 1.4 s
Avoid long main-thread tasks 5 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 10 ms
Server Backend Latencies 480 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 180 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
68

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Valve Corporation div.row > div.col_2 > h5.business_name > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
3D Character Artist div.row > div.job_opening > a > h5.job_title

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col_3 > div.steam_logo > a > img div.col_3 > div.steam_logo > a > img
div.col_3 > div.steamworks_logo > a > img div.col_3 > div.steamworks_logo > a > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header_inner_wrapper > div.top_nav > div.logo > a div.header_inner_wrapper > div.top_nav > div.logo > a
div.row > div.col_3 > div.steam_logo > a div.row > div.col_3 > div.steam_logo > a
div.row > div.col_3 > div.steamworks_logo > a div.row > div.col_3 > div.steamworks_logo > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
Buttons have an accessible name
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Document has a `<title>` element
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Document has a main landmark.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<!DOCTYPE html>Syntax not understood
2<html>Syntax not understood
3 <head>Syntax not understood
4 <meta charset="utf-8">Syntax not understood
5 <link rel="shortcut icon" href="https://cdn.akamai.steamstatic.com/valvesoftware/images/favicon.ico">Unknown directive
6 <title>Valve Corporation</title>Syntax not understood
7 <meta name="viewport" content="width=device-width, initial-scale=1">Syntax not understood
8 <meta http-equiv="X-UA-Compatible" content="IE=edge">Syntax not understood
9 <meta charset="utf-8">Syntax not understood
11 <meta name="description" content="We make games, Steam, and hardware. Join Us.">Syntax not understood
12 <meta name="image" content="https://cdn.akamai.steamstatic.com/valvesoftware/images/valve-og.jpg">Unknown directive
14 <meta itemprop="name" content="Valve Corporation">Syntax not understood
15 <meta itemprop="description" content="We make games, Steam, and hardware. Join Us.">Syntax not understood
16 <meta itemprop="image" content="https://cdn.akamai.steamstatic.com/valvesoftware/images/valve-og.jpg">Unknown directive
18 <meta name="og:title" content="Valve Corporation">Unknown directive
19 <meta name="og:description" content="We make games, Steam, and hardware. Join Us.">Unknown directive
20 <meta name="og:image" content="https://cdn.akamai.steamstatic.com/valvesoftware/images/valve-og.jpg">Unknown directive
21 <meta name="og:site_name" content="Valve Corporation">Unknown directive
22 <meta name="og:type" content="website">Unknown directive
24 <meta name="twitter:card" value="summary">Unknown directive
26 <link href="https://www.valvesoftware.com/public/css/global.css?v=lmcEcZ-F-ilx&amp;_cdn=akamai" rel="stylesheet" type="text/css">Unknown directive
27<link href="https://www.valvesoftware.com/public/css/fonts.css?v=xSaYcfyOLADT&amp;_cdn=akamai" rel="stylesheet" type="text/css">Unknown directive
28<link href="https://www.valvesoftware.com/public/css/forms.css?v=50QYppCbB4ar&amp;_cdn=akamai" rel="stylesheet" type="text/css">Unknown directive
29<link href="https://www.valvesoftware.com/public/css/jobs.css?v=Gwqg1pBmxEi2&amp;_cdn=akamai" rel="stylesheet" type="text/css">Unknown directive
30<script type="text/javascript" src="https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&amp;_cdn=akamai"></script>Unknown directive
31<script type="text/javascript">$J = jQuery.noConflict();</script><script type="text/javascript" src="https://www.valvesoftware.com/en/public/javascript/valvesoftware.js?v=Yw_MCZWiaUD0&amp;_cdn=akamai"></script>Unknown directive
33<script type="text/javascript">Syntax not understood
34</script><script type="text/javascript" src="https://www.valvesoftware.com/en/public/javascript/jobs.js?v=KKAPM5KmPVH7&amp;_cdn=akamai"></script>Unknown directive
36 <script src='https://www.google.com/recaptcha/api.js'></script>Unknown directive
38 </head>Syntax not understood
39 <body data-vsapp-context="home">Syntax not understood
40 <div class="site_wrapper">Syntax not understood
41 <header class="main_header">Syntax not understood
42 <div class="header_inner_wrapper">Syntax not understood
43 <div class="top_nav">Syntax not understood
44 <div class="logo">Syntax not understood
45 <a href="https://www.valvesoftware.com/en/about">Unknown directive
46 <svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 436 121.06"><defs><clipPath id="clip-path"><rect class="cls-1" x="1" y="-1" width="436" height="124.06"/></clipPath></defs><polygon class="cls-2" points="142.57 36.95 134.84 67.88 151.01 67.88 142.57 36.95"/><g class="cls-3"><path class="cls-2" d="M47.1,24.6l14.1,55.3L75,24.6h15.2L67.9,97.8H54.5L32.7,24.6H47.1z M132.4,24.6h19.7l20.8,73.3h-14.8 l-4.9-18.3h-21.9c0,0-3.8,14.7-4.6,18c-4.4,0.3-15.1,0-15.1,0L132.4,24.6z M208.4,24.6h14.4v60.9h30.7v12.3h-45.1L208.4,24.6z M285.9,24.6L300,79.2l13.7-54.6h14.8l-22.2,73.3h-13l-22.2-73.3L285.9,24.6z M389.5,24.6v9.5h-19.7v10.6h18v9.5h-18v10.9h19.7 v9.5h-30.7v-50H389.5z M0,123.2h436V-1.1H0"/></g></svg>Unknown directive
47 </a>Syntax not understood
48 </div>Syntax not understood
49 </div>Syntax not understood
50 </div>Syntax not understood
51 <div id="header_background_video">Syntax not understood
52 </div>Syntax not understood
53 </header>Syntax not understood
54 <div id="content_outer_wrapper">Syntax not understood
55 <div id="content_inner_wrapper">Syntax not understood
56 <div id="content" data-content-context="home"><div id="page_background_videos">Syntax not understood
57 <video playsinline muted class="background_video" poster="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_fullsize.jpg">Unknown directive
58 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_fullsize.webm" type="video/webm">Unknown directive
59 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_fullsize.mp4" type="video/mp4">Unknown directive
60 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_small.webm" type="video/webm">Unknown directive
61 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_small.mp4" type="video/mp4">Unknown directive
62 </video>Syntax not understood
63 <video playsinline muted class="background_video" poster="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_fullsize.jpg">Unknown directive
64 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_fullsize.webm" type="video/webm">Unknown directive
65 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_fullsize.mp4" type="video/mp4">Unknown directive
66 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_small.webm" type="video/webm">Unknown directive
67 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_small.mp4" type="video/mp4">Unknown directive
68 </video>Syntax not understood
69 <video playsinline muted class="background_video" poster="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_fullsize.jpg">Unknown directive
70 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_fullsize.webm" type="video/webm">Unknown directive
71 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_fullsize.mp4" type="video/mp4">Unknown directive
72 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_small.webm" type="video/webm">Unknown directive
73 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_small.mp4" type="video/mp4">Unknown directive
74 </video>Syntax not understood
75 </div>Syntax not understood
77<section id="jobs" class="job_skills full_bleed">Syntax not understood
78 <div class="section_inner_wrapper">Syntax not understood
79 <div class="search_form_wrapper">Syntax not understood
80 <div class="row search_header">Syntax not understood
81 <div class="col_6 job_skills_title">Syntax not understood
82 <h3>Syntax not understood
83 <a href="about">We make games, Steam, and hardware. Join us.</a> </h3>Syntax not understood
84 <p>Syntax not understood
85 We aren't a typical company&mdash;which is why you're here, right? As a flat company without hierarchy and job titles, we don't usually hire for specific roles. (Though we sometimes do!) Opportunities at Valve run broad and deep. We're always hiring highly experienced collaborators who are the best at what they do, across the following areas: </p>Unknown directive
86 </div>Syntax not understood
87 <div class="col_5 col_offset_1 search_form">Syntax not understood
88 <form>Syntax not understood
89 <input type="text"Syntax not understood
90 placeholder="Search Jobs">Syntax not understood
91 <button type="button" class="clear_button">Clear</button>Syntax not understood
92 <button class="search_button">Search</button>Syntax not understood
93 </form>Syntax not understood
94 </div>Syntax not understood
95 </div>Syntax not understood
96 <div class="search_form_results_wrapper">Syntax not understood
97 <div class="search_form_results_inner_wrapper">Syntax not understood
98 <div class="search_form_results job_openings">Syntax not understood
99 <div class="row">Syntax not understood
100 </div>Syntax not understood
101 </div>Syntax not understood
102 </div>Syntax not understood
103 </div>Syntax not understood
104 </div>Syntax not understood
105 <div class="row">Syntax not understood
106 <div class="col_12">Syntax not understood
107 <ul class="job_tags">Syntax not understood
108 <li class="job_tag" data-job_cat="art">Syntax not understood
109 <a href="#">Art</a>Syntax not understood
110 <div class="job_openings_wrapper">Syntax not understood
111 <div class="job_openings_inner_wrapper row">Syntax not understood
114 <div class="col_12 job_openings_category_description">Syntax not understood
115 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
117 <div class="col_12">Syntax not understood
118 <div class="job_openings">Syntax not understood
119 <div class="row">Syntax not understood
120 <div class="job_opening col_3">Syntax not understood
121 <a href="https://www.valvesoftware.com/en/jobs?job_id=2">Unknown directive
122 <h5 class="job_title">Syntax not understood
123 3D Character Artist </h5>Syntax not understood
124 </a>Syntax not understood
125 </div>Syntax not understood
127 <div class="job_opening col_3">Syntax not understood
128 <a href="https://www.valvesoftware.com/en/jobs?job_id=30">Unknown directive
129 <h5 class="job_title">Syntax not understood
130 Animator </h5>Syntax not understood
131 </a>Syntax not understood
132 </div>Syntax not understood
134 <div class="job_opening col_3">Syntax not understood
135 <a href="https://www.valvesoftware.com/en/jobs?job_id=43">Unknown directive
136 <h5 class="job_title">Syntax not understood
137 Effects Artist </h5>Syntax not understood
138 </a>Syntax not understood
139 </div>Syntax not understood
141 <div class="job_opening col_3">Syntax not understood
142 <a href="https://www.valvesoftware.com/en/jobs?job_id=49">Unknown directive
143 <h5 class="job_title">Syntax not understood
144 3D Environment Artist </h5>Syntax not understood
145 </a>Syntax not understood
146 </div>Syntax not understood
148 </div>Syntax not understood
149 <div class="row">Syntax not understood
150 </div>Syntax not understood
151 </div>Syntax not understood
152</div>Syntax not understood
154 </div>Syntax not understood
155 </div>Syntax not understood
156 </li>Syntax not understood
157 <li class="job_tag" data-job_cat="audio">Syntax not understood
158 <a href="#">Audio</a>Syntax not understood
159 <div class="job_openings_wrapper">Syntax not understood
160 <div class="job_openings_inner_wrapper row">Syntax not understood
163 <div class="col_12 job_openings_category_description">Syntax not understood
164 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
166 <div class="col_12">Syntax not understood
167 <div class="job_openings">Syntax not understood
168 <div class="row">Syntax not understood
169 <div class="job_opening col_3">Syntax not understood
170 <a href="https://www.valvesoftware.com/en/jobs?job_id=18">Unknown directive
171 <h5 class="job_title">Syntax not understood
172 Sound Designer </h5>Syntax not understood
173 </a>Syntax not understood
174 </div>Syntax not understood
176 <div class="job_opening col_3">Syntax not understood
177 <a href="https://www.valvesoftware.com/en/jobs?job_id=85">Unknown directive
178 <h5 class="job_title">Syntax not understood
179 Audio Software Engineer </h5>Syntax not understood
180 </a>Syntax not understood
181 </div>Syntax not understood
183 </div>Syntax not understood
184 </div>Syntax not understood
185</div>Syntax not understood
187 </div>Syntax not understood
188 </div>Syntax not understood
189 </li>Syntax not understood
190 <li class="job_tag" data-job_cat="business-development">Syntax not understood
191 <a href="#">Business Development</a>Syntax not understood
192 <div class="job_openings_wrapper">Syntax not understood
193 <div class="job_openings_inner_wrapper row">Syntax not understood
196 <div class="col_12 job_openings_category_description">Syntax not understood
197 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
199 <div class="col_12">Syntax not understood
200 <div class="job_openings">Syntax not understood
201 <div class="row">Syntax not understood
202 <div class="job_opening col_3">Syntax not understood
203 <a href="https://www.valvesoftware.com/en/jobs?job_id=20">Unknown directive
204 <h5 class="job_title">Syntax not understood
205 Business Development<span class="job_division">Steam Team</span> </h5>Syntax not understood
206 </a>Syntax not understood
207 </div>Syntax not understood
209 <div class="job_opening col_3">Syntax not understood
210 <a href="https://www.valvesoftware.com/en/jobs?job_id=21">Unknown directive
211 <h5 class="job_title">Syntax not understood
212 Steam Partner Technical Account Manager </h5>Syntax not understood
213 </a>Syntax not understood
214 </div>Syntax not understood
216 </div>Syntax not understood
217 </div>Syntax not understood
218</div>Syntax not understood
220 </div>Syntax not understood
221 </div>Syntax not understood
222 </li>Syntax not understood
223 <li class="job_tag" data-job_cat="customer-support">Syntax not understood
224 <a href="#">Customer Support</a>Syntax not understood
225 <div class="job_openings_wrapper">Syntax not understood
226 <div class="job_openings_inner_wrapper row">Syntax not understood
229 <div class="col_12 job_openings_category_description">Syntax not understood
230 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
232 <div class="col_12">Syntax not understood
233 <div class="job_openings">Syntax not understood
234 <div class="row">Syntax not understood
235 <div class="job_opening col_3">Syntax not understood
236 <a href="https://www.valvesoftware.com/en/jobs?job_id=113">Unknown directive
237 <h5 class="job_title">Syntax not understood
238 Steam Support Leadership </h5>Syntax not understood
239 </a>Syntax not understood
240 </div>Syntax not understood
242 </div>Syntax not understood
243 </div>Syntax not understood
244</div>Syntax not understood
246 </div>Syntax not understood
247 </div>Syntax not understood
248 </li>Syntax not understood
249 <li class="job_tag" data-job_cat="finance">Syntax not understood
250 <a href="#">Finance</a>Syntax not understood
251 <div class="job_openings_wrapper">Syntax not understood
252 <div class="job_openings_inner_wrapper row">Syntax not understood
255 <div class="col_12 job_openings_category_description">Syntax not understood
256 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
258 <div class="col_12">Syntax not understood
259 <div class="job_openings">Syntax not understood
260 <div class="row">Syntax not understood
261 <div class="job_opening col_3">Syntax not understood
262 <a href="https://www.valvesoftware.com/en/jobs?job_id=108">Unknown directive
263 <h5 class="job_title">Syntax not understood
264 Outbound Royalty Payments Professional </h5>Syntax not understood
265 </a>Syntax not understood
266 </div>Syntax not understood
268 <div class="job_opening col_3">Syntax not understood
269 <a href="https://www.valvesoftware.com/en/jobs?job_id=109">Unknown directive
270 <h5 class="job_title">Syntax not understood
271 Hardware Finance & Accounting Professional </h5>Syntax not understood
272 </a>Syntax not understood
273 </div>Syntax not understood
275 <div class="job_opening col_3">Syntax not understood
276 <a href="https://www.valvesoftware.com/en/jobs?job_id=62">Unknown directive
277 <h5 class="job_title">Syntax not understood
278 Finance<span class="job_division">Other</span> </h5>Syntax not understood
279 </a>Syntax not understood
280 </div>Syntax not understood
282 </div>Syntax not understood
283 </div>Syntax not understood
284</div>Syntax not understood
286 </div>Syntax not understood
287 </div>Syntax not understood
288 </li>Syntax not understood
289 <li class="job_tag" data-job_cat="game-design">Syntax not understood
290 <a href="#">Game Design</a>Syntax not understood
291 <div class="job_openings_wrapper">Syntax not understood
292 <div class="job_openings_inner_wrapper row">Syntax not understood
295 <div class="col_12 job_openings_category_description">Syntax not understood
296 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
298 <div class="col_12">Syntax not understood
299 <div class="job_openings">Syntax not understood
300 <div class="row">Syntax not understood
301 <div class="job_opening col_3">Syntax not understood
302 <a href="https://www.valvesoftware.com/en/jobs?job_id=9">Unknown directive
303 <h5 class="job_title">Syntax not understood
304 Level Designer </h5>Syntax not understood
305 </a>Syntax not understood
306 </div>Syntax not understood
308 <div class="job_opening col_3">Syntax not understood
309 <a href="https://www.valvesoftware.com/en/jobs?job_id=18">Unknown directive
310 <h5 class="job_title">Syntax not understood
311 Sound Designer </h5>Syntax not understood
312 </a>Syntax not understood
313 </div>Syntax not understood
315 <div class="job_opening col_3">Syntax not understood
316 <a href="https://www.valvesoftware.com/en/jobs?job_id=51">Unknown directive
317 <h5 class="job_title">Syntax not understood
318 Game Development Software Engineer </h5>Syntax not understood
319 </a>Syntax not understood
320 </div>Syntax not understood
322 <div class="job_opening col_3">Syntax not understood
323 <a href="https://www.valvesoftware.com/en/jobs?job_id=63">Unknown directive
324 <h5 class="job_title">Syntax not understood
325 Game Design<span class="job_division">Other</span> </h5>Syntax not understood
326 </a>Syntax not understood
327 </div>Syntax not understood
329 </div>Syntax not understood
330 <div class="row">Syntax not understood
331 </div>Syntax not understood
332 </div>Syntax not understood
333</div>Syntax not understood
335 </div>Syntax not understood
336 </div>Syntax not understood
337 </li>Syntax not understood
338 <li class="job_tag" data-job_cat="hardware">Syntax not understood
339 <a href="#">Hardware</a>Syntax not understood
340 <div class="job_openings_wrapper">Syntax not understood
341 <div class="job_openings_inner_wrapper row">Syntax not understood
344 <div class="col_12 job_openings_category_description">Syntax not understood
345 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
347 <div class="col_12">Syntax not understood
348 <div class="job_openings">Syntax not understood
349 <div class="row">Syntax not understood
350 <div class="job_opening col_3">Syntax not understood
351 <a href="https://www.valvesoftware.com/en/jobs?job_id=5">Unknown directive
352 <h5 class="job_title">Syntax not understood
353 Electrical Engineer </h5>Syntax not understood
354 </a>Syntax not understood
355 </div>Syntax not understood
357 <div class="job_opening col_3">Syntax not understood
358 <a href="https://www.valvesoftware.com/en/jobs?job_id=7">Unknown directive
359 <h5 class="job_title">Syntax not understood
360 Industrial Designer </h5>Syntax not understood
361 </a>Syntax not understood
362 </div>Syntax not understood
364 <div class="job_opening col_3">Syntax not understood
365 <a href="https://www.valvesoftware.com/en/jobs?job_id=41">Unknown directive
366 <h5 class="job_title">Syntax not understood
367 Software Engineer for HW </h5>Syntax not understood
368 </a>Syntax not understood
369 </div>Syntax not understood
371 <div class="job_opening col_3">Syntax not understood
372 <a href="https://www.valvesoftware.com/en/jobs?job_id=116">Unknown directive
373 <h5 class="job_title">Syntax not understood
374 Thermal Engineer </h5>Syntax not understood
375 </a>Syntax not understood
376 </div>Syntax not understood
378 </div>Syntax not understood
379 <div class="row">Syntax not understood
380 </div>Syntax not understood
381 </div>Syntax not understood
382</div>Syntax not understood
384 </div>Syntax not understood
385 </div>Syntax not understood
386 </li>Syntax not understood
387 <li class="job_tag" data-job_cat="legal">Syntax not understood
388 <a href="#">Legal</a>Syntax not understood
389 <div class="job_openings_wrapper">Syntax not understood
390 <div class="job_openings_inner_wrapper row">Syntax not understood
393 <div class="col_12 job_openings_category_description">Syntax not understood
394 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
396 <div class="col_12">Syntax not understood
397 <div class="job_openings">Syntax not understood
398 <div class="row">Syntax not understood
399 <div class="job_opening col_3">Syntax not understood
400 <a href="https://www.valvesoftware.com/en/jobs?job_id=117">Unknown directive
401 <h5 class="job_title">Syntax not understood
402 Legal Team </h5>Syntax not understood
403 </a>Syntax not understood
404 </div>Syntax not understood
406 </div>Syntax not understood
407 </div>Syntax not understood
408</div>Syntax not understood
410 </div>Syntax not understood
411 </div>Syntax not understood
412 </li>Syntax not understood
413 <li class="job_tag" data-job_cat="product-design">Syntax not understood
414 <a href="#">Product Design</a>Syntax not understood
415 <div class="job_openings_wrapper">Syntax not understood
416 <div class="job_openings_inner_wrapper row">Syntax not understood
419 <div class="col_12 job_openings_category_description">Syntax not understood
420 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
422 <div class="col_12">Syntax not understood
423 <div class="job_openings">Syntax not understood
424 <div class="row">Syntax not understood
425 <div class="job_opening col_3">Syntax not understood
426 <a href="https://www.valvesoftware.com/en/jobs?job_id=7">Unknown directive
427 <h5 class="job_title">Syntax not understood
428 Industrial Designer </h5>Syntax not understood
429 </a>Syntax not understood
430 </div>Syntax not understood
432 <div class="job_opening col_3">Syntax not understood
433 <a href="https://www.valvesoftware.com/en/jobs?job_id=8">Unknown directive
434 <h5 class="job_title">Syntax not understood
435 Design<span class="job_division">Visual & User Experience</span> </h5>Syntax not understood
436 </a>Syntax not understood
437 </div>Syntax not understood
439 <div class="job_opening col_3">Syntax not understood
440 <a href="https://www.valvesoftware.com/en/jobs?job_id=66">Unknown directive
441 <h5 class="job_title">Syntax not understood
442 Design<span class="job_division">Other</span> </h5>Syntax not understood
443 </a>Syntax not understood
444 </div>Syntax not understood
446 </div>Syntax not understood
447 </div>Syntax not understood
448</div>Syntax not understood
450 </div>Syntax not understood
451 </div>Syntax not understood
452 </li>Syntax not understood
453 <li class="job_tag" data-job_cat="software-engineering">Syntax not understood
454 <a href="#">Software Engineering</a>Syntax not understood
455 <div class="job_openings_wrapper">Syntax not understood
456 <div class="job_openings_inner_wrapper row">Syntax not understood
459 <div class="col_12 job_openings_category_description">Syntax not understood
460 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
462 <div class="col_12">Syntax not understood
463 <div class="job_openings">Syntax not understood
464 <div class="row">Syntax not understood
465 <div class="job_opening col_3">Syntax not understood
466 <a href="https://www.valvesoftware.com/en/jobs?job_id=14">Unknown directive
467 <h5 class="job_title">Syntax not understood
468 Steam Software Engineer </h5>Syntax not understood
469 </a>Syntax not understood
470 </div>Syntax not understood
472 <div class="job_opening col_3">Syntax not understood
473 <a href="https://www.valvesoftware.com/en/jobs?job_id=16">Unknown directive
474 <h5 class="job_title">Syntax not understood
475 Steam Database Administrator </h5>Syntax not understood
476 </a>Syntax not understood
477 </div>Syntax not understood
479 <div class="job_opening col_3">Syntax not understood
480 <a href="https://www.valvesoftware.com/en/jobs?job_id=21">Unknown directive
481 <h5 class="job_title">Syntax not understood
482 Steam Partner Technical Account Manager </h5>Syntax not understood
483 </a>Syntax not understood
484 </div>Syntax not understood
486 <div class="job_opening col_3">Syntax not understood
487 <a href="https://www.valvesoftware.com/en/jobs?job_id=41">Unknown directive
488 <h5 class="job_title">Syntax not understood
489 Software Engineer for HW </h5>Syntax not understood
490 </a>Syntax not understood
491 </div>Syntax not understood
493 </div>Syntax not understood
494 <div class="row">Syntax not understood
495 <div class="job_opening col_3">Syntax not understood
496 <a href="https://www.valvesoftware.com/en/jobs?job_id=51">Unknown directive
497 <h5 class="job_title">Syntax not understood
498 Game Development Software Engineer </h5>Syntax not understood
499 </a>Syntax not understood
500 </div>Syntax not understood
502 <div class="job_opening col_3">Syntax not understood
503 <a href="https://www.valvesoftware.com/en/jobs?job_id=52">Unknown directive
504 <h5 class="job_title">Syntax not understood
505 Computer Vision Software Engineer </h5>Syntax not understood
506 </a>Syntax not understood
507 </div>Syntax not understood
509 <div class="job_opening col_3">Syntax not understood
510 <a href="https://www.valvesoftware.com/en/jobs?job_id=85">Unknown directive
511 <h5 class="job_title">Syntax not understood
512 Audio Software Engineer </h5>Syntax not understood
513 </a>Syntax not understood
514 </div>Syntax not understood
516 <div class="job_opening col_3">Syntax not understood
517 <a href="https://www.valvesoftware.com/en/jobs?job_id=57">Unknown directive
518 <h5 class="job_title">Syntax not understood
519 Software Engineering<span class="job_division">Other</span> </h5>Syntax not understood
520 </a>Syntax not understood
521 </div>Syntax not understood
523 </div>Syntax not understood
524 <div class="row">Syntax not understood
525 </div>Syntax not understood
526 </div>Syntax not understood
527</div>Syntax not understood
529 </div>Syntax not understood
530 </div>Syntax not understood
531 </li>Syntax not understood
532 <li class="job_tag" data-job_cat="technical-infrastructure">Syntax not understood
533 <a href="#">Technical Infrastructure</a>Syntax not understood
534 <div class="job_openings_wrapper">Syntax not understood
535 <div class="job_openings_inner_wrapper row">Syntax not understood
538 <div class="col_12 job_openings_category_description">Syntax not understood
539 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
541 <div class="col_12">Syntax not understood
542 <div class="job_openings">Syntax not understood
543 <div class="row">Syntax not understood
544 <div class="job_opening col_3">Syntax not understood
545 <a href="https://www.valvesoftware.com/en/jobs?job_id=16">Unknown directive
546 <h5 class="job_title">Syntax not understood
547 Steam Database Administrator </h5>Syntax not understood
548 </a>Syntax not understood
549 </div>Syntax not understood
551 </div>Syntax not understood
552 </div>Syntax not understood
553</div>Syntax not understood
555 </div>Syntax not understood
556 </div>Syntax not understood
557 </li>Syntax not understood
558 <li class="job_tag empty_answer"><a href="https://www.valvesoftware.com/en/jobs?job_id=27">Did we miss something?</a></li>Unknown directive
559 </ul>Syntax not understood
560 </div>Syntax not understood
561 </div>Syntax not understood
562 </div>Syntax not understood
563</section>Syntax not understood
566 </div>Syntax not understood
567 <footer class="main_footer">Syntax not understood
568 <div class="main_footer_inner_wrapper">Syntax not understood
569 <div class="row">Syntax not understood
570 <div class="col_2">Syntax not understood
571 <h5 class="business_name"><a href="https://www.valvesoftware.com/en/about">Valve Corporation</a></h5>Unknown directive
572 </div>Syntax not understood
573 <div class="col_6 col_offset_1 footer_nav_wrapper">Syntax not understood
574 <nav class="footer_nav">Syntax not understood
575 <ul>Syntax not understood
576 <li>Contact <ul>Syntax not understood
577 <li>Syntax not understood
578 <a href="https://www.valvesoftware.com/en/people">People</a>Unknown directive
579 </li>Syntax not understood
580 <li>Syntax not understood
581 <a href="https://www.valvesoftware.com/en/press/inquiries">Press Inquiries</a>Unknown directive
582 </li>Syntax not understood
583 </ul>Syntax not understood
584 </li>Syntax not understood
585 <li>Stuff <ul>Syntax not understood
586 <li>Syntax not understood
587 <a href="https://www.valvesoftware.com/en/about">About Us</a>Unknown directive
588 </li>Syntax not understood
589 <li>Syntax not understood
590 <a href="https://www.valvesoftware.com/en/">Jobs</a>Unknown directive
591 </li>Syntax not understood
592 <li>Syntax not understood
593 <a href="//partner.steamgames.com/"Syntax not understood
594 target="_blank">Steam Partners</a>Syntax not understood
595 </li>Syntax not understood
596 <li>Syntax not understood
597 <a href="https://www.valvesoftware.com/en/publications">Publications</a>Unknown directive
598 </li>Syntax not understood
599 </ul>Syntax not understood
600 </li>Syntax not understood
601 <li>More Stuff <ul>Syntax not understood
602 <li>Syntax not understood
603 <a href="https://www.valvesoftware.com/en/legal/site-terms-of-use">Site Terms of Use</a>Unknown directive
604 </li>Syntax not understood
605 <li>Syntax not understood
606 <a href="//store.steampowered.com/privacy_agreement/"Syntax not understood
607 target="_blank">Privacy Policy</a>Syntax not understood
608 </li>Syntax not understood
609 <li>Syntax not understood
610 <a href="https://www.valvesoftware.com/en/security">Security</a>Unknown directive
611 </li>Syntax not understood
612 <li>Syntax not understood
613 <a href="//store.steampowered.com/legal"Syntax not understood
614 target="_blank">Legal</a>Syntax not understood
615 </li>Syntax not understood
616 </ul>Syntax not understood
617 </li>Syntax not understood
618 </ul>Syntax not understood
619 </nav>Syntax not understood
620 </div>Syntax not understood
621 <div class="col_3 footer_steam_logos">Syntax not understood
622 <div class="steam_logo">Syntax not understood
623 <a href="http://store.steampowered.com/" target="_blank">Unknown directive
624 <img src="https://cdn.akamai.steamstatic.com/valvesoftware/images/steam_logo_footer.png">Unknown directive
625 </a>Syntax not understood
626 </div>Syntax not understood
627 <div class="steamworks_logo">Syntax not understood
628 <a href="https://partner.steamgames.com/" target="_blank">Unknown directive
629 <img src="https://cdn.akamai.steamstatic.com/valvesoftware/images/steamworks_logo_footer.png">Unknown directive
630 </a>Syntax not understood
631 </div>Syntax not understood
632 </div>Syntax not understood
633 </div>Syntax not understood
634 </div>Syntax not understood
635 </footer>Syntax not understood
636 </div>Syntax not understood
637 </div>Syntax not understood
638 </div>Syntax not understood
639 </body>Syntax not understood
640</html>Syntax not understood

To appear in search results, crawlers need access to your app.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col_3 > div.steam_logo > a > img div.col_3 > div.steam_logo > a > img
div.col_3 > div.steamworks_logo > a > img div.col_3 > div.steamworks_logo > a > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

90
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
61
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

963 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.76 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

28 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.53 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.76 s

Detailed Report

Audit breakdown by category with detailed findings.

90

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:3.454 source:map[column:9837 line:2 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:39.42 source:map[type:text value:[unattributed]]] map[reflowTime:0.799 source:map[column:21731 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]] map[reflowTime:0.393 source:map[column:21828 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]] map[reflowTime:0.314 source:map[column:22058 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]] map[reflowTime:0.208 source:map[column:22485 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]] map[reflowTime:1.002 source:map[column:22640 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]] map[reflowTime:0.316 source:map[column:22785 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]] map[reflowTime:0.422 source:map[column:93259 line:1 type:source-location url:https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&_cdn=akamai urlProvider:network]]]

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.valvesoftware.com/en/http/1.1
www.valvesoftware.com/public/css/global.css?v=lmcEcZ-F-ilx&_cdn=akamaihttp/1.1
www.valvesoftware.com/public/css/fonts.css?v=xSaYcfyOLADT&_cdn=akamaihttp/1.1
www.valvesoftware.com/public/css/forms.css?v=50QYppCbB4ar&_cdn=akamaihttp/1.1
www.valvesoftware.com/public/css/jobs.css?v=Gwqg1pBmxEi2&_cdn=akamaihttp/1.1
/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5z...http/1.1
/en/public/javascript/valvesoftware.js?v=Yw_MCZWiaUD0&_cd...http/1.1
www.valvesoftware.com/en/public/javascript/jobs.js?v=KKAPM5KmPVH7&_cdn=akamaihttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_fullsize.jpghttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_fullsize.jpghttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_fullsize.jpghttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/steam_logo_footer.pnghttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/steamworks_logo_footer.pnghttp/1.1
www.valvesoftware.com/public/css/fonts/apercu-medium.WOFFhttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/search.pnghttp/1.1
www.valvesoftware.com/public/css/fonts/apercu-black.WOFFhttp/1.1
www.valvesoftware.com/public/css/fonts/apercu-regular.WOFFhttp/1.1
www.valvesoftware.com/public/css/fonts/apercu-bold.WOFFhttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_fullsize.webmhttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_fullsize.webmhttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_fullsize.webmhttp/1.1
cdn.akamai.steamstatic.com/valvesoftware/images/favicon.icohttp/1.1

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 200 ms 262.3 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.col_3 > div.steamworks_logo > a > img div.col_3 > div.steamworks_logo > a > img
cdn.akamai.steamstatic.com/valvesoftware/images/steamworks_logo_footer.png
div.col_3 > div.steam_logo > a > img div.col_3 > div.steam_logo > a > img
cdn.akamai.steamstatic.com/valvesoftware/images/steam_logo_footer.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 609 ms
Time to Interactive 1.8 s
Max Potential First Input Delay 80 ms
Layout shift culprits
Optimize DOM size
Improve image delivery
LCP breakdown
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
JavaScript execution time 0.1 s
Minimizes main-thread work 0.4 s
Avoid long main-thread tasks 1 long task found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 10 ms
Server Backend Latencies 170 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 190 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
61

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Valve Corporation div.row > div.col_2 > h5.business_name > a
Contact People Press Inquiries div.col_6 > nav.footer_nav > ul > li
Stuff About Us Jobs Steam Partners Publications div.col_6 > nav.footer_nav > ul > li
More Stuff Site Terms of Use Privacy Policy Security Legal div.col_6 > nav.footer_nav > ul > li

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
3D Character Artist div.row > div.job_opening > a > h5.job_title

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col_3 > div.steam_logo > a > img div.col_3 > div.steam_logo > a > img
div.col_3 > div.steamworks_logo > a > img div.col_3 > div.steamworks_logo > a > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header_inner_wrapper > div.top_nav > div.logo > a div.header_inner_wrapper > div.top_nav > div.logo > a
div.row > div.col_3 > div.steam_logo > a div.row > div.col_3 > div.steam_logo > a
div.row > div.col_3 > div.steamworks_logo > a div.row > div.col_3 > div.steamworks_logo > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Steam Partners li > ul > li > a
Publications li > ul > li > a
Security li > ul > li > a
Legal li > ul > li > a

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
Buttons have an accessible name
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Document has a `<title>` element
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Document has a main landmark.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<!DOCTYPE html>Syntax not understood
2<html>Syntax not understood
3 <head>Syntax not understood
4 <meta charset="utf-8">Syntax not understood
5 <link rel="shortcut icon" href="https://cdn.akamai.steamstatic.com/valvesoftware/images/favicon.ico">Unknown directive
6 <title>Valve Corporation</title>Syntax not understood
7 <meta name="viewport" content="width=device-width, initial-scale=1">Syntax not understood
8 <meta http-equiv="X-UA-Compatible" content="IE=edge">Syntax not understood
9 <meta charset="utf-8">Syntax not understood
11 <meta name="description" content="We make games, Steam, and hardware. Join Us.">Syntax not understood
12 <meta name="image" content="https://cdn.akamai.steamstatic.com/valvesoftware/images/valve-og.jpg">Unknown directive
14 <meta itemprop="name" content="Valve Corporation">Syntax not understood
15 <meta itemprop="description" content="We make games, Steam, and hardware. Join Us.">Syntax not understood
16 <meta itemprop="image" content="https://cdn.akamai.steamstatic.com/valvesoftware/images/valve-og.jpg">Unknown directive
18 <meta name="og:title" content="Valve Corporation">Unknown directive
19 <meta name="og:description" content="We make games, Steam, and hardware. Join Us.">Unknown directive
20 <meta name="og:image" content="https://cdn.akamai.steamstatic.com/valvesoftware/images/valve-og.jpg">Unknown directive
21 <meta name="og:site_name" content="Valve Corporation">Unknown directive
22 <meta name="og:type" content="website">Unknown directive
24 <meta name="twitter:card" value="summary">Unknown directive
26 <link href="https://www.valvesoftware.com/public/css/global.css?v=lmcEcZ-F-ilx&amp;_cdn=akamai" rel="stylesheet" type="text/css">Unknown directive
27<link href="https://www.valvesoftware.com/public/css/fonts.css?v=xSaYcfyOLADT&amp;_cdn=akamai" rel="stylesheet" type="text/css">Unknown directive
28<link href="https://www.valvesoftware.com/public/css/forms.css?v=50QYppCbB4ar&amp;_cdn=akamai" rel="stylesheet" type="text/css">Unknown directive
29<link href="https://www.valvesoftware.com/public/css/jobs.css?v=Gwqg1pBmxEi2&amp;_cdn=akamai" rel="stylesheet" type="text/css">Unknown directive
30<script type="text/javascript" src="https://www.valvesoftware.com/en/public/shared/javascript/jquery-1.8.3.min.js?v=NXam5zydzNu8&amp;_cdn=akamai"></script>Unknown directive
31<script type="text/javascript">$J = jQuery.noConflict();</script><script type="text/javascript" src="https://www.valvesoftware.com/en/public/javascript/valvesoftware.js?v=Yw_MCZWiaUD0&amp;_cdn=akamai"></script>Unknown directive
33<script type="text/javascript">Syntax not understood
34</script><script type="text/javascript" src="https://www.valvesoftware.com/en/public/javascript/jobs.js?v=KKAPM5KmPVH7&amp;_cdn=akamai"></script>Unknown directive
36 <script src='https://www.google.com/recaptcha/api.js'></script>Unknown directive
38 </head>Syntax not understood
39 <body data-vsapp-context="home">Syntax not understood
40 <div class="site_wrapper">Syntax not understood
41 <header class="main_header">Syntax not understood
42 <div class="header_inner_wrapper">Syntax not understood
43 <div class="top_nav">Syntax not understood
44 <div class="logo">Syntax not understood
45 <a href="https://www.valvesoftware.com/en/about">Unknown directive
46 <svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 436 121.06"><defs><clipPath id="clip-path"><rect class="cls-1" x="1" y="-1" width="436" height="124.06"/></clipPath></defs><polygon class="cls-2" points="142.57 36.95 134.84 67.88 151.01 67.88 142.57 36.95"/><g class="cls-3"><path class="cls-2" d="M47.1,24.6l14.1,55.3L75,24.6h15.2L67.9,97.8H54.5L32.7,24.6H47.1z M132.4,24.6h19.7l20.8,73.3h-14.8 l-4.9-18.3h-21.9c0,0-3.8,14.7-4.6,18c-4.4,0.3-15.1,0-15.1,0L132.4,24.6z M208.4,24.6h14.4v60.9h30.7v12.3h-45.1L208.4,24.6z M285.9,24.6L300,79.2l13.7-54.6h14.8l-22.2,73.3h-13l-22.2-73.3L285.9,24.6z M389.5,24.6v9.5h-19.7v10.6h18v9.5h-18v10.9h19.7 v9.5h-30.7v-50H389.5z M0,123.2h436V-1.1H0"/></g></svg>Unknown directive
47 </a>Syntax not understood
48 </div>Syntax not understood
49 </div>Syntax not understood
50 </div>Syntax not understood
51 <div id="header_background_video">Syntax not understood
52 </div>Syntax not understood
53 </header>Syntax not understood
54 <div id="content_outer_wrapper">Syntax not understood
55 <div id="content_inner_wrapper">Syntax not understood
56 <div id="content" data-content-context="home"><div id="page_background_videos">Syntax not understood
57 <video playsinline muted class="background_video" poster="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_fullsize.jpg">Unknown directive
58 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_fullsize.webm" type="video/webm">Unknown directive
59 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_fullsize.mp4" type="video/mp4">Unknown directive
60 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_small.webm" type="video/webm">Unknown directive
61 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_01_small.mp4" type="video/mp4">Unknown directive
62 </video>Syntax not understood
63 <video playsinline muted class="background_video" poster="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_fullsize.jpg">Unknown directive
64 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_fullsize.webm" type="video/webm">Unknown directive
65 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_fullsize.mp4" type="video/mp4">Unknown directive
66 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_small.webm" type="video/webm">Unknown directive
67 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_02_small.mp4" type="video/mp4">Unknown directive
68 </video>Syntax not understood
69 <video playsinline muted class="background_video" poster="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_fullsize.jpg">Unknown directive
70 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_fullsize.webm" type="video/webm">Unknown directive
71 <source class="fullsize" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_fullsize.mp4" type="video/mp4">Unknown directive
72 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_small.webm" type="video/webm">Unknown directive
73 <source class="mobile" src="https://cdn.akamai.steamstatic.com/valvesoftware/images/videos/hero_03_small.mp4" type="video/mp4">Unknown directive
74 </video>Syntax not understood
75 </div>Syntax not understood
77<section id="jobs" class="job_skills full_bleed">Syntax not understood
78 <div class="section_inner_wrapper">Syntax not understood
79 <div class="search_form_wrapper">Syntax not understood
80 <div class="row search_header">Syntax not understood
81 <div class="col_6 job_skills_title">Syntax not understood
82 <h3>Syntax not understood
83 <a href="about">We make games, Steam, and hardware. Join us.</a> </h3>Syntax not understood
84 <p>Syntax not understood
85 We aren't a typical company&mdash;which is why you're here, right? As a flat company without hierarchy and job titles, we don't usually hire for specific roles. (Though we sometimes do!) Opportunities at Valve run broad and deep. We're always hiring highly experienced collaborators who are the best at what they do, across the following areas: </p>Unknown directive
86 </div>Syntax not understood
87 <div class="col_5 col_offset_1 search_form">Syntax not understood
88 <form>Syntax not understood
89 <input type="text"Syntax not understood
90 placeholder="Search Jobs">Syntax not understood
91 <button type="button" class="clear_button">Clear</button>Syntax not understood
92 <button class="search_button">Search</button>Syntax not understood
93 </form>Syntax not understood
94 </div>Syntax not understood
95 </div>Syntax not understood
96 <div class="search_form_results_wrapper">Syntax not understood
97 <div class="search_form_results_inner_wrapper">Syntax not understood
98 <div class="search_form_results job_openings">Syntax not understood
99 <div class="row">Syntax not understood
100 </div>Syntax not understood
101 </div>Syntax not understood
102 </div>Syntax not understood
103 </div>Syntax not understood
104 </div>Syntax not understood
105 <div class="row">Syntax not understood
106 <div class="col_12">Syntax not understood
107 <ul class="job_tags">Syntax not understood
108 <li class="job_tag" data-job_cat="art">Syntax not understood
109 <a href="#">Art</a>Syntax not understood
110 <div class="job_openings_wrapper">Syntax not understood
111 <div class="job_openings_inner_wrapper row">Syntax not understood
114 <div class="col_12 job_openings_category_description">Syntax not understood
115 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
117 <div class="col_12">Syntax not understood
118 <div class="job_openings">Syntax not understood
119 <div class="row">Syntax not understood
120 <div class="job_opening col_3">Syntax not understood
121 <a href="https://www.valvesoftware.com/en/jobs?job_id=2">Unknown directive
122 <h5 class="job_title">Syntax not understood
123 3D Character Artist </h5>Syntax not understood
124 </a>Syntax not understood
125 </div>Syntax not understood
127 <div class="job_opening col_3">Syntax not understood
128 <a href="https://www.valvesoftware.com/en/jobs?job_id=30">Unknown directive
129 <h5 class="job_title">Syntax not understood
130 Animator </h5>Syntax not understood
131 </a>Syntax not understood
132 </div>Syntax not understood
134 <div class="job_opening col_3">Syntax not understood
135 <a href="https://www.valvesoftware.com/en/jobs?job_id=43">Unknown directive
136 <h5 class="job_title">Syntax not understood
137 Effects Artist </h5>Syntax not understood
138 </a>Syntax not understood
139 </div>Syntax not understood
141 <div class="job_opening col_3">Syntax not understood
142 <a href="https://www.valvesoftware.com/en/jobs?job_id=49">Unknown directive
143 <h5 class="job_title">Syntax not understood
144 3D Environment Artist </h5>Syntax not understood
145 </a>Syntax not understood
146 </div>Syntax not understood
148 </div>Syntax not understood
149 <div class="row">Syntax not understood
150 </div>Syntax not understood
151 </div>Syntax not understood
152</div>Syntax not understood
154 </div>Syntax not understood
155 </div>Syntax not understood
156 </li>Syntax not understood
157 <li class="job_tag" data-job_cat="audio">Syntax not understood
158 <a href="#">Audio</a>Syntax not understood
159 <div class="job_openings_wrapper">Syntax not understood
160 <div class="job_openings_inner_wrapper row">Syntax not understood
163 <div class="col_12 job_openings_category_description">Syntax not understood
164 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
166 <div class="col_12">Syntax not understood
167 <div class="job_openings">Syntax not understood
168 <div class="row">Syntax not understood
169 <div class="job_opening col_3">Syntax not understood
170 <a href="https://www.valvesoftware.com/en/jobs?job_id=18">Unknown directive
171 <h5 class="job_title">Syntax not understood
172 Sound Designer </h5>Syntax not understood
173 </a>Syntax not understood
174 </div>Syntax not understood
176 <div class="job_opening col_3">Syntax not understood
177 <a href="https://www.valvesoftware.com/en/jobs?job_id=85">Unknown directive
178 <h5 class="job_title">Syntax not understood
179 Audio Software Engineer </h5>Syntax not understood
180 </a>Syntax not understood
181 </div>Syntax not understood
183 </div>Syntax not understood
184 </div>Syntax not understood
185</div>Syntax not understood
187 </div>Syntax not understood
188 </div>Syntax not understood
189 </li>Syntax not understood
190 <li class="job_tag" data-job_cat="business-development">Syntax not understood
191 <a href="#">Business Development</a>Syntax not understood
192 <div class="job_openings_wrapper">Syntax not understood
193 <div class="job_openings_inner_wrapper row">Syntax not understood
196 <div class="col_12 job_openings_category_description">Syntax not understood
197 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
199 <div class="col_12">Syntax not understood
200 <div class="job_openings">Syntax not understood
201 <div class="row">Syntax not understood
202 <div class="job_opening col_3">Syntax not understood
203 <a href="https://www.valvesoftware.com/en/jobs?job_id=20">Unknown directive
204 <h5 class="job_title">Syntax not understood
205 Business Development<span class="job_division">Steam Team</span> </h5>Syntax not understood
206 </a>Syntax not understood
207 </div>Syntax not understood
209 <div class="job_opening col_3">Syntax not understood
210 <a href="https://www.valvesoftware.com/en/jobs?job_id=21">Unknown directive
211 <h5 class="job_title">Syntax not understood
212 Steam Partner Technical Account Manager </h5>Syntax not understood
213 </a>Syntax not understood
214 </div>Syntax not understood
216 </div>Syntax not understood
217 </div>Syntax not understood
218</div>Syntax not understood
220 </div>Syntax not understood
221 </div>Syntax not understood
222 </li>Syntax not understood
223 <li class="job_tag" data-job_cat="customer-support">Syntax not understood
224 <a href="#">Customer Support</a>Syntax not understood
225 <div class="job_openings_wrapper">Syntax not understood
226 <div class="job_openings_inner_wrapper row">Syntax not understood
229 <div class="col_12 job_openings_category_description">Syntax not understood
230 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
232 <div class="col_12">Syntax not understood
233 <div class="job_openings">Syntax not understood
234 <div class="row">Syntax not understood
235 <div class="job_opening col_3">Syntax not understood
236 <a href="https://www.valvesoftware.com/en/jobs?job_id=113">Unknown directive
237 <h5 class="job_title">Syntax not understood
238 Steam Support Leadership </h5>Syntax not understood
239 </a>Syntax not understood
240 </div>Syntax not understood
242 </div>Syntax not understood
243 </div>Syntax not understood
244</div>Syntax not understood
246 </div>Syntax not understood
247 </div>Syntax not understood
248 </li>Syntax not understood
249 <li class="job_tag" data-job_cat="finance">Syntax not understood
250 <a href="#">Finance</a>Syntax not understood
251 <div class="job_openings_wrapper">Syntax not understood
252 <div class="job_openings_inner_wrapper row">Syntax not understood
255 <div class="col_12 job_openings_category_description">Syntax not understood
256 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
258 <div class="col_12">Syntax not understood
259 <div class="job_openings">Syntax not understood
260 <div class="row">Syntax not understood
261 <div class="job_opening col_3">Syntax not understood
262 <a href="https://www.valvesoftware.com/en/jobs?job_id=108">Unknown directive
263 <h5 class="job_title">Syntax not understood
264 Outbound Royalty Payments Professional </h5>Syntax not understood
265 </a>Syntax not understood
266 </div>Syntax not understood
268 <div class="job_opening col_3">Syntax not understood
269 <a href="https://www.valvesoftware.com/en/jobs?job_id=109">Unknown directive
270 <h5 class="job_title">Syntax not understood
271 Hardware Finance & Accounting Professional </h5>Syntax not understood
272 </a>Syntax not understood
273 </div>Syntax not understood
275 <div class="job_opening col_3">Syntax not understood
276 <a href="https://www.valvesoftware.com/en/jobs?job_id=62">Unknown directive
277 <h5 class="job_title">Syntax not understood
278 Finance<span class="job_division">Other</span> </h5>Syntax not understood
279 </a>Syntax not understood
280 </div>Syntax not understood
282 </div>Syntax not understood
283 </div>Syntax not understood
284</div>Syntax not understood
286 </div>Syntax not understood
287 </div>Syntax not understood
288 </li>Syntax not understood
289 <li class="job_tag" data-job_cat="game-design">Syntax not understood
290 <a href="#">Game Design</a>Syntax not understood
291 <div class="job_openings_wrapper">Syntax not understood
292 <div class="job_openings_inner_wrapper row">Syntax not understood
295 <div class="col_12 job_openings_category_description">Syntax not understood
296 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
298 <div class="col_12">Syntax not understood
299 <div class="job_openings">Syntax not understood
300 <div class="row">Syntax not understood
301 <div class="job_opening col_3">Syntax not understood
302 <a href="https://www.valvesoftware.com/en/jobs?job_id=9">Unknown directive
303 <h5 class="job_title">Syntax not understood
304 Level Designer </h5>Syntax not understood
305 </a>Syntax not understood
306 </div>Syntax not understood
308 <div class="job_opening col_3">Syntax not understood
309 <a href="https://www.valvesoftware.com/en/jobs?job_id=18">Unknown directive
310 <h5 class="job_title">Syntax not understood
311 Sound Designer </h5>Syntax not understood
312 </a>Syntax not understood
313 </div>Syntax not understood
315 <div class="job_opening col_3">Syntax not understood
316 <a href="https://www.valvesoftware.com/en/jobs?job_id=51">Unknown directive
317 <h5 class="job_title">Syntax not understood
318 Game Development Software Engineer </h5>Syntax not understood
319 </a>Syntax not understood
320 </div>Syntax not understood
322 <div class="job_opening col_3">Syntax not understood
323 <a href="https://www.valvesoftware.com/en/jobs?job_id=63">Unknown directive
324 <h5 class="job_title">Syntax not understood
325 Game Design<span class="job_division">Other</span> </h5>Syntax not understood
326 </a>Syntax not understood
327 </div>Syntax not understood
329 </div>Syntax not understood
330 <div class="row">Syntax not understood
331 </div>Syntax not understood
332 </div>Syntax not understood
333</div>Syntax not understood
335 </div>Syntax not understood
336 </div>Syntax not understood
337 </li>Syntax not understood
338 <li class="job_tag" data-job_cat="hardware">Syntax not understood
339 <a href="#">Hardware</a>Syntax not understood
340 <div class="job_openings_wrapper">Syntax not understood
341 <div class="job_openings_inner_wrapper row">Syntax not understood
344 <div class="col_12 job_openings_category_description">Syntax not understood
345 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
347 <div class="col_12">Syntax not understood
348 <div class="job_openings">Syntax not understood
349 <div class="row">Syntax not understood
350 <div class="job_opening col_3">Syntax not understood
351 <a href="https://www.valvesoftware.com/en/jobs?job_id=5">Unknown directive
352 <h5 class="job_title">Syntax not understood
353 Electrical Engineer </h5>Syntax not understood
354 </a>Syntax not understood
355 </div>Syntax not understood
357 <div class="job_opening col_3">Syntax not understood
358 <a href="https://www.valvesoftware.com/en/jobs?job_id=7">Unknown directive
359 <h5 class="job_title">Syntax not understood
360 Industrial Designer </h5>Syntax not understood
361 </a>Syntax not understood
362 </div>Syntax not understood
364 <div class="job_opening col_3">Syntax not understood
365 <a href="https://www.valvesoftware.com/en/jobs?job_id=41">Unknown directive
366 <h5 class="job_title">Syntax not understood
367 Software Engineer for HW </h5>Syntax not understood
368 </a>Syntax not understood
369 </div>Syntax not understood
371 <div class="job_opening col_3">Syntax not understood
372 <a href="https://www.valvesoftware.com/en/jobs?job_id=116">Unknown directive
373 <h5 class="job_title">Syntax not understood
374 Thermal Engineer </h5>Syntax not understood
375 </a>Syntax not understood
376 </div>Syntax not understood
378 </div>Syntax not understood
379 <div class="row">Syntax not understood
380 </div>Syntax not understood
381 </div>Syntax not understood
382</div>Syntax not understood
384 </div>Syntax not understood
385 </div>Syntax not understood
386 </li>Syntax not understood
387 <li class="job_tag" data-job_cat="legal">Syntax not understood
388 <a href="#">Legal</a>Syntax not understood
389 <div class="job_openings_wrapper">Syntax not understood
390 <div class="job_openings_inner_wrapper row">Syntax not understood
393 <div class="col_12 job_openings_category_description">Syntax not understood
394 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
396 <div class="col_12">Syntax not understood
397 <div class="job_openings">Syntax not understood
398 <div class="row">Syntax not understood
399 <div class="job_opening col_3">Syntax not understood
400 <a href="https://www.valvesoftware.com/en/jobs?job_id=117">Unknown directive
401 <h5 class="job_title">Syntax not understood
402 Legal Team </h5>Syntax not understood
403 </a>Syntax not understood
404 </div>Syntax not understood
406 </div>Syntax not understood
407 </div>Syntax not understood
408</div>Syntax not understood
410 </div>Syntax not understood
411 </div>Syntax not understood
412 </li>Syntax not understood
413 <li class="job_tag" data-job_cat="product-design">Syntax not understood
414 <a href="#">Product Design</a>Syntax not understood
415 <div class="job_openings_wrapper">Syntax not understood
416 <div class="job_openings_inner_wrapper row">Syntax not understood
419 <div class="col_12 job_openings_category_description">Syntax not understood
420 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
422 <div class="col_12">Syntax not understood
423 <div class="job_openings">Syntax not understood
424 <div class="row">Syntax not understood
425 <div class="job_opening col_3">Syntax not understood
426 <a href="https://www.valvesoftware.com/en/jobs?job_id=7">Unknown directive
427 <h5 class="job_title">Syntax not understood
428 Industrial Designer </h5>Syntax not understood
429 </a>Syntax not understood
430 </div>Syntax not understood
432 <div class="job_opening col_3">Syntax not understood
433 <a href="https://www.valvesoftware.com/en/jobs?job_id=8">Unknown directive
434 <h5 class="job_title">Syntax not understood
435 Design<span class="job_division">Visual & User Experience</span> </h5>Syntax not understood
436 </a>Syntax not understood
437 </div>Syntax not understood
439 <div class="job_opening col_3">Syntax not understood
440 <a href="https://www.valvesoftware.com/en/jobs?job_id=66">Unknown directive
441 <h5 class="job_title">Syntax not understood
442 Design<span class="job_division">Other</span> </h5>Syntax not understood
443 </a>Syntax not understood
444 </div>Syntax not understood
446 </div>Syntax not understood
447 </div>Syntax not understood
448</div>Syntax not understood
450 </div>Syntax not understood
451 </div>Syntax not understood
452 </li>Syntax not understood
453 <li class="job_tag" data-job_cat="software-engineering">Syntax not understood
454 <a href="#">Software Engineering</a>Syntax not understood
455 <div class="job_openings_wrapper">Syntax not understood
456 <div class="job_openings_inner_wrapper row">Syntax not understood
459 <div class="col_12 job_openings_category_description">Syntax not understood
460 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
462 <div class="col_12">Syntax not understood
463 <div class="job_openings">Syntax not understood
464 <div class="row">Syntax not understood
465 <div class="job_opening col_3">Syntax not understood
466 <a href="https://www.valvesoftware.com/en/jobs?job_id=14">Unknown directive
467 <h5 class="job_title">Syntax not understood
468 Steam Software Engineer </h5>Syntax not understood
469 </a>Syntax not understood
470 </div>Syntax not understood
472 <div class="job_opening col_3">Syntax not understood
473 <a href="https://www.valvesoftware.com/en/jobs?job_id=16">Unknown directive
474 <h5 class="job_title">Syntax not understood
475 Steam Database Administrator </h5>Syntax not understood
476 </a>Syntax not understood
477 </div>Syntax not understood
479 <div class="job_opening col_3">Syntax not understood
480 <a href="https://www.valvesoftware.com/en/jobs?job_id=21">Unknown directive
481 <h5 class="job_title">Syntax not understood
482 Steam Partner Technical Account Manager </h5>Syntax not understood
483 </a>Syntax not understood
484 </div>Syntax not understood
486 <div class="job_opening col_3">Syntax not understood
487 <a href="https://www.valvesoftware.com/en/jobs?job_id=41">Unknown directive
488 <h5 class="job_title">Syntax not understood
489 Software Engineer for HW </h5>Syntax not understood
490 </a>Syntax not understood
491 </div>Syntax not understood
493 </div>Syntax not understood
494 <div class="row">Syntax not understood
495 <div class="job_opening col_3">Syntax not understood
496 <a href="https://www.valvesoftware.com/en/jobs?job_id=51">Unknown directive
497 <h5 class="job_title">Syntax not understood
498 Game Development Software Engineer </h5>Syntax not understood
499 </a>Syntax not understood
500 </div>Syntax not understood
502 <div class="job_opening col_3">Syntax not understood
503 <a href="https://www.valvesoftware.com/en/jobs?job_id=52">Unknown directive
504 <h5 class="job_title">Syntax not understood
505 Computer Vision Software Engineer </h5>Syntax not understood
506 </a>Syntax not understood
507 </div>Syntax not understood
509 <div class="job_opening col_3">Syntax not understood
510 <a href="https://www.valvesoftware.com/en/jobs?job_id=85">Unknown directive
511 <h5 class="job_title">Syntax not understood
512 Audio Software Engineer </h5>Syntax not understood
513 </a>Syntax not understood
514 </div>Syntax not understood
516 <div class="job_opening col_3">Syntax not understood
517 <a href="https://www.valvesoftware.com/en/jobs?job_id=57">Unknown directive
518 <h5 class="job_title">Syntax not understood
519 Software Engineering<span class="job_division">Other</span> </h5>Syntax not understood
520 </a>Syntax not understood
521 </div>Syntax not understood
523 </div>Syntax not understood
524 <div class="row">Syntax not understood
525 </div>Syntax not understood
526 </div>Syntax not understood
527</div>Syntax not understood
529 </div>Syntax not understood
530 </div>Syntax not understood
531 </li>Syntax not understood
532 <li class="job_tag" data-job_cat="technical-infrastructure">Syntax not understood
533 <a href="#">Technical Infrastructure</a>Syntax not understood
534 <div class="job_openings_wrapper">Syntax not understood
535 <div class="job_openings_inner_wrapper row">Syntax not understood
538 <div class="col_12 job_openings_category_description">Syntax not understood
539 <b>We're always hiring.</b><p>We hire people with broad skill sets who also exhibit deep expertise. While nobody at Valve has a job title, we do have certain fields that we're always looking to hire in.</p> </div>Syntax not understood
541 <div class="col_12">Syntax not understood
542 <div class="job_openings">Syntax not understood
543 <div class="row">Syntax not understood
544 <div class="job_opening col_3">Syntax not understood
545 <a href="https://www.valvesoftware.com/en/jobs?job_id=16">Unknown directive
546 <h5 class="job_title">Syntax not understood
547 Steam Database Administrator </h5>Syntax not understood
548 </a>Syntax not understood
549 </div>Syntax not understood
551 </div>Syntax not understood
552 </div>Syntax not understood
553</div>Syntax not understood
555 </div>Syntax not understood
556 </div>Syntax not understood
557 </li>Syntax not understood
558 <li class="job_tag empty_answer"><a href="https://www.valvesoftware.com/en/jobs?job_id=27">Did we miss something?</a></li>Unknown directive
559 </ul>Syntax not understood
560 </div>Syntax not understood
561 </div>Syntax not understood
562 </div>Syntax not understood
563</section>Syntax not understood
566 </div>Syntax not understood
567 <footer class="main_footer">Syntax not understood
568 <div class="main_footer_inner_wrapper">Syntax not understood
569 <div class="row">Syntax not understood
570 <div class="col_2">Syntax not understood
571 <h5 class="business_name"><a href="https://www.valvesoftware.com/en/about">Valve Corporation</a></h5>Unknown directive
572 </div>Syntax not understood
573 <div class="col_6 col_offset_1 footer_nav_wrapper">Syntax not understood
574 <nav class="footer_nav">Syntax not understood
575 <ul>Syntax not understood
576 <li>Contact <ul>Syntax not understood
577 <li>Syntax not understood
578 <a href="https://www.valvesoftware.com/en/people">People</a>Unknown directive
579 </li>Syntax not understood
580 <li>Syntax not understood
581 <a href="https://www.valvesoftware.com/en/press/inquiries">Press Inquiries</a>Unknown directive
582 </li>Syntax not understood
583 </ul>Syntax not understood
584 </li>Syntax not understood
585 <li>Stuff <ul>Syntax not understood
586 <li>Syntax not understood
587 <a href="https://www.valvesoftware.com/en/about">About Us</a>Unknown directive
588 </li>Syntax not understood
589 <li>Syntax not understood
590 <a href="https://www.valvesoftware.com/en/">Jobs</a>Unknown directive
591 </li>Syntax not understood
592 <li>Syntax not understood
593 <a href="//partner.steamgames.com/"Syntax not understood
594 target="_blank">Steam Partners</a>Syntax not understood
595 </li>Syntax not understood
596 <li>Syntax not understood
597 <a href="https://www.valvesoftware.com/en/publications">Publications</a>Unknown directive
598 </li>Syntax not understood
599 </ul>Syntax not understood
600 </li>Syntax not understood
601 <li>More Stuff <ul>Syntax not understood
602 <li>Syntax not understood
603 <a href="https://www.valvesoftware.com/en/legal/site-terms-of-use">Site Terms of Use</a>Unknown directive
604 </li>Syntax not understood
605 <li>Syntax not understood
606 <a href="//store.steampowered.com/privacy_agreement/"Syntax not understood
607 target="_blank">Privacy Policy</a>Syntax not understood
608 </li>Syntax not understood
609 <li>Syntax not understood
610 <a href="https://www.valvesoftware.com/en/security">Security</a>Unknown directive
611 </li>Syntax not understood
612 <li>Syntax not understood
613 <a href="//store.steampowered.com/legal"Syntax not understood
614 target="_blank">Legal</a>Syntax not understood
615 </li>Syntax not understood
616 </ul>Syntax not understood
617 </li>Syntax not understood
618 </ul>Syntax not understood
619 </nav>Syntax not understood
620 </div>Syntax not understood
621 <div class="col_3 footer_steam_logos">Syntax not understood
622 <div class="steam_logo">Syntax not understood
623 <a href="http://store.steampowered.com/" target="_blank">Unknown directive
624 <img src="https://cdn.akamai.steamstatic.com/valvesoftware/images/steam_logo_footer.png">Unknown directive
625 </a>Syntax not understood
626 </div>Syntax not understood
627 <div class="steamworks_logo">Syntax not understood
628 <a href="https://partner.steamgames.com/" target="_blank">Unknown directive
629 <img src="https://cdn.akamai.steamstatic.com/valvesoftware/images/steamworks_logo_footer.png">Unknown directive
630 </a>Syntax not understood
631 </div>Syntax not understood
632 </div>Syntax not understood
633 </div>Syntax not understood
634 </div>Syntax not understood
635 </footer>Syntax not understood
636 </div>Syntax not understood
637 </div>Syntax not understood
638 </div>Syntax not understood
639 </body>Syntax not understood
640</html>Syntax not understood

To appear in search results, crawlers need access to your app.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col_3 > div.steam_logo > a > img div.col_3 > div.steam_logo > a > img
div.col_3 > div.steamworks_logo > a > img div.col_3 > div.steamworks_logo > a > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback