login.brightree.net/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3DDme.Web.Client%26redirect_uri%3Dhttps%253A%252F%252Fbrightree.net%252Fsignin-oidc%26response_mode%3Dform_post%26response_type%3Dcode%2520id_token%26scope%3DDme.User%2520openid%2520profile%2520DocumentManagementAPI%2520Brightree.Survey.Api%26state%3DOpenIdConnect.AuthenticationProperties%253Dzha496p8yARY0up9QlgkLmi4wmE9PTxLy5fXD7GubxSHUpX-b1YIvgVZRcGBADRboEzW3gxrJNGLLT65NjVEYZGcFU-wz---IlhBJKtsojWzdq0aobLHgia_HzS8x7vZFycOFtNCA7R6sFiwZC2grMc87AsvAgrTHNiLkQlRpNLThO3CSJ-Lgl_6-fZspWRPfbFMKj0k9Mxia-AtzWM8peb1L-e_DQq28HtM6U8S6Uw%26nonce%3D639281083397715178.NWNlYWQ1NzYtZTY0Ni00N2MyLWE5NzEtMzQ2ODk5NWM1OTVmNzA4MzdhODUtY2UwYi00MmQ3LThlYTAtZjNjODk3MDQzM2Vh%26prompt%3Dlogin%26x-client-SKU%3DID_NET461%26x-client-ver%3D5.7.0.0%26suppressed_prompt%3Dlogin speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 15:52 UTC. Grade A (93/100), with the screenshots, the timings and the fixes that matter.

https://login.brightree.net/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3DDme.Web.Client%26redirect_uri%3Dhttps%253A%252F%252Fbrightree.net%252Fsignin-oidc%26response_mode%3Dform_post%26response_type%3Dcode%2520id_token%26scope%3DDme.User%2520openid%2520profile%2520DocumentManagementAPI%2520Brightree.Survey.Api%26state%3DOpenIdConnect.AuthenticationProperties%253Dzha496p8yARY0up9QlgkLmi4wmE9PTxLy5fXD7GubxSHUpX-b1YIvgVZRcGBADRboEzW3gxrJNGLLT65NjVEYZGcFU-wz---IlhBJKtsojWzdq0aobLHgia_HzS8x7vZFycOFtNCA7R6sFiwZC2grMc87AsvAgrTHNiLkQlRpNLThO3CSJ-Lgl_6-fZspWRPfbFMKj0k9Mxia-AtzWM8peb1L-e_DQq28HtM6U8S6Uw%26nonce%3D639281083397715178.NWNlYWQ1NzYtZTY0Ni00N2MyLWE5NzEtMzQ2ODk5NWM1OTVmNzA4MzdhODUtY2UwYi00MmQ3LThlYTAtZjNjODk3MDQzM2Vh%26prompt%3Dlogin%26x-client-SKU%3DID_NET461%26x-client-ver%3D5.7.0.0%26suppressed_prompt%3Dlogin

20 October 2026 at 15:52 UTC · Free test · report pt_a9df6c3da791

Re-test this page Test your own site

Grade

93/100

Performance94/100

Structure92/100

14 audit(s) passed, 2 need work

First byte (TTFB)422 msmeasured from this server

Fully loaded1.44 sfirst byte + slowest asset

Requests12document + assets

Page weight4.8 KBcompressed transfer

HTML document4.8 KBdeflate

ProtocolHTTP/2Microsoft-IIS/10.0

Where the first byte went

DNS lookup 65 ms 15%
TCP connect 71 ms 17%
Server wait 286 ms 68%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 53% of 4,999 pages tested here422 ms against a median of 449 ms

Page weightlighter than 96% of 4,999 pages tested here4.8 KB against a median of 650.5 KB

Fully loadedfaster than 74% of 4,999 pages tested here1.44 s against a median of 1.84 s

Requestssends fewer requests than 86% of 4,999 pages tested here12 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

The first byte arrived in 422 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 4.8 KB over 12 request(s), which is lean.
The HTML itself arrives deflate-compressed.
It runs over HTTP/2, so the assets share a connection instead of opening one each.
The largest element painted at 808 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.079), so nothing jumps under the reader's cursor.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of login.brightree.net — **Mobile** 390 × 844 · 132.5 KB · page is 1202 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint808 msgood is under 2.5 s

Cumulative layout shift0.079under 0.1 is stable

Total blocking timenone over 50 mslong tasks during load

First contentful paint672 msfirst content on screen

Browser page weight292.1 KB13 request(s), scripts included

Failed requests1blocked or unreachable

Largest contentful paint808 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.079

Goodgood under 0.1, poor over 0.25

Total blocking timenone over 50 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Transfer size, compressed as sent. 12 request(s) in total, 4.8 KB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 422 ms. Of that, 286 ms was the server thinking and 136 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Avoid extra redirects

medium impact

2 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.