> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/export/project-score.md).

# Project Score

The Project Score is an automated audit of your playable, run every time you open the [Export dialog](/play/export/export-partners.md). It checks your project against a set of proven best-practice rules and rates it across four categories, so you can catch performance and conversion problems before the ad goes live.

### The Four Categories

Each category is scored from **0 to 100** and rated **Great** (90+), **Good** (60+), **Okay** (30+), or **Poor** (below 30). Metrics render green at 60 and above, yellow from 30–59, and red below 30.

* **Performance** — how quickly your playable loads and runs. Driven by [file size](/play/export/file-size.md) and asset optimization.
* **Responsivity** — how well the playable adapts to different screens and [orientations](/play/settings/orientations.md).
* **Engagement** — how available your CTA links are throughout the experience.
* **Best Practices** — concept, design, and visual appeal, such as use of animation.

### How Scoring Works

Each category starts at 100 and every detected issue subtracts points (never below 0). Issues come in three severities:

* **Errors** — the biggest deductions, from **20 to 75 points**. Example: no CTA layer anywhere (−75), an End Card without a CTA (−50), total file size over 5MB (−50).
* **Warnings** — moderate deductions, from **5 to 30 points**. Example: a missing orientation (−30), CTAs absent from too many scenes (−30), no intro animations (−30), file size over 4MB (−20), an asset larger than 1024×1024 (−5 each).
* **Suggestions** — advisory only, **0 points**. Example: a CTA not triggered by Single Tap, autoplaying videos, or unassigned End Card scenes.

### Reading and Fixing Issues

The score appears on the right side of the Export dialog as four radial metrics. Click **View Issues** to expand the full list, grouped by category. Each issue shows its severity, a description of what to change, and — where applicable — a fix link that closes the dialog and jumps you straight to the relevant layer or panel.

{% hint style="info" %}
If any category is rated **Poor** when you export, PLAY shows a confirmation dialog warning that performance may suffer. Exporting is not blocked — but it isn't recommended. And if all four categories hit 90+, you get confetti.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.craftsmanplus.com/play/export/project-score.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.