---
title: "Set LogLevel of Blazor"
description: "Blazor is a bit talkative when it comes to the Developer Console. \nPageSpeed Insights for example does complain:\n> Browser errors were logged to the console\n\nThe fix is easy. "
updated: 2026-07-12
tags: ["Blazor"]
canonical: "https://steven-giesel.com/blogPost/1cfa82eb-1108-4355-8815-615b094bf9ec/set-loglevel-of-blazor"
---

# Set LogLevel of Blazor

Blazor is a bit talkative when it comes to the Developer Console. 
PageSpeed Insights for example does complain:
> Browser errors were logged to the console

The fix is easy. 

## Setup logging in `Blazor.start`

The default template scaffolds something like that:
```html
<script src="_framework/blazor.web.js">
```

But we can easily configure this manually:
```html
<script>
    Blazor.start({
        logLevel: "none",
        circuit: {
            configureSignalR: builder => {
                builder.configureLogging("none");
            }
        }
    });
</script>
```

This would stop any logging whatsoever. A better version might be ti use `critical` instead of `none`. More can be found here: https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/logging?view=aspnetcore-10.0#signalr-client-logging-with-the-signalr-client-builder