> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/infinity/service-catalog/hot-air.md).

# Webshop & Benchmark Analysis

### Webshop & Benchmark Analysis​

### What it is

Evaluation of your shop based on different categories in comparison, to your competitors/industry. Recommended when doing a shop relaunch.

**Categories Reviewed in Analysis​**

* Homepage – UX/Design, Ease of finding information​
* Search – Location of search barm Search Result Quality​
* Suggest – Design, Content​
* Navigation – Level structure, Relevance, UX, Completeness, Result Quality​
* Product Detail Page – Ease of finding information, UX/Design, Sharing Options
* Shopping Cart – Preventing exits, up/-cross selling​
* Check-Out – UX/Convenience​
* General – Personalization, Merchandising, Trust Factors​
* Mobile – Taking advantage of the platform, UX/Design, Filters

### What’s in for you

* Demonstration of competitive advantages and disadvantages in comparison to the same industry.​
* Suggestions on solutions from other industries to gain competitive advantages through a better customer journey​.
* Suggestion of quick wins that can be implemented with FactFinder, plus more time-consuming topics, that need to be adjusted in the frontend.​

### How it’s done

#### Estimated time​

* 5 hours Webshop Analysis ​
* 1 hour Websession to discuss results​
* 2.5 hours per Benchmark Analysis​

#### Deliverables​

PDF report on Optimization Suggestions on your online shop – from start page to check-out. Delivered by​ a FactFinder Consultant​.

​

​


---

# 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://docs.fact-finder.com/infinity/service-catalog/hot-air.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.
