Page summary

Summary

Metric	Value
Page metrics
Performance Score	86
Total Page Transfer Size	198.8 KB
Requests	14
Timing metrics
TTFB [median]	164 ms
First Paint [median]	364 ms
Fully Loaded [median]	487 ms
Google Web Vitals
TTFB [median]	164 ms
First Contentful Paint (FCP) [median]	364 ms
Largest Contentful Paint (LCP) [median]	364 ms
Cumulative Layout Shift (CLS) [median]	0.00
Visual Metrics
First Visual Change [median]	367 ms
Speed Index [median]	367 ms
Visual Complete 85% [median]	367 ms
Visual Complete 99% [median]	367 ms
Last Visual Change [median]	367 ms

Timings Summary

Waterfall

Run 3 SpeedIndex median

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

0.4 sFirst Contentful Paint 364 msLCP <P> 364 msFirst Visual Change 367 msLast Visual Change 367 msVisual Complete 85% 367 msVisual Complete 95% 367 msVisual Complete 99% 367 ms

Coach

The coach helps you find performance problems on your web page using web performance best practice rules. And gives you advice on privacy and best practices. Tested using Coach-core version 8.1.1.

Coach score

• Total score 86
• Performance score 86
• Privacy score 91
• Best practice score 76

Performance advice (86)

Show/hide details

Title	Advice	Score
Inline CSS for faster first render (inlineCss)	The page has both inline CSS and CSS requests even though it uses a HTTP/2-ish connection. If you have many users on slow connections, it can be better to only inline the CSS. Run your own tests and check the waterfall graph to see what happens.	95
Description: In the early days of the Internet, inlining CSS was one of the ugliest things you can do. That has changed if you want your page to start rendering fast for your user. Always inline the critical CSS when you use HTTP/1 and HTTP/2 (avoid doing CSS requests that block rendering) and lazy load and cache the rest of the CSS. It is a little more complicated when using HTTP/2. Does your server support HTTP push? Then maybe that can help. Do you have a lot of users on a slow connection and are serving large chunks of HTML? Then it could be better to use the inline technique, becasue some servers always prioritize HTML content over CSS so the user needs to download the HTML first, before the CSS is downloaded.
Avoid Frontend single point of failures (spof)	The page has 5 requests inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head.	80
Description: A page can be stopped from loading in the browser if a single JavaScript, CSS, and in some cases a font, couldn't be fetched or is loading really slowly (the white screen of death). That is a scenario you really want to avoid. Never load 3rd-party components synchronously inside of the head tag.
Offenders: https://cdn.jsdelivr.net/npm/bootstrap@5.1.3/dist/css/bootstrap.min.css https://cdn.jsdelivr.net/npm/bootstrap-icons@1.7.2/font/bootstrap-icons.css https://unpkg.com/bootstrap-table@1.21.2/dist/bootstrap-table.min.css https://cdn.jsdelivr.net/npm/bootstrap-icons@1.10.3/font/bootstrap-icons.css https://unpkg.com/leaflet@1.9.3/dist/leaflet.css
Avoid doing redirects (assetsRedirects)	The page has 1 redirect. 1 of the redirects are from the base domain, please fix them!	90
Description: A redirect is one extra step for the user to download the asset. Avoid that if you want to be fast. Redirects are even more of a showstopper on mobile.
Offenders: https://allinbn.com/
Avoid extra requests by setting cache headers (cacheHeaders)	The page has 3 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 3.1 kB the next access.	70
Description: The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request.
Offenders: https://allinbn.com/ https://allinbn.com/static/site.webmanifest https://allinbn.com/static/favicon.ico
Long cache headers is good (cacheHeadersLong)	The page has 1 request that have a shorter cache time than 30 days (but still a cache time).	99
Description: Setting a cache header is good. Setting a long cache header (at least 30 days) is even better beacause then it will stay long in the browser cache. But what do you do if that asset change? Rename it and the browser will pick up the new version.
Offenders: https://cdn.jsdelivr.net/npm/jquery/dist/jquery.min.js
Always compress text content (compressAssets)	The page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead.	90
Description: In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith.
Offenders: URL Transfer size Content size https://allinbn.com/about/?next=/ 3.0 KB 6.4 KB
Avoid redirecting the main document (documentRedirect)	The main document gets redirected 1 time(s). Remove those redirect and make the page faster!	0
Description: You should never ever redirect the main document, because it will make the page load slower for the user. Well, you should redirect the user if the user tries to use HTTP and there's an HTTPS version of the page. The coach checks for that. :)
Offenders: https://allinbn.com/
The favicon should be small and cacheable (favicon)	The favicon has no cache time.	50
Description: It is easy to make the favicon big but please avoid doing that, because every browser will then perform an unnecessarily large download. And make sure the cache headers are set for a long time for the favicon. It is easy to miss since it's another content type.
Offenders: https://allinbn.com/static/favicon.ico
Total JavaScript size shouldn't be too big (javascriptSize)	The total JavaScript transfer size is 146 kB and the uncompressed size is 470.3 kB. This is quite large.	50
Description: A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks?
Offenders: URL Transfer size Content size https://cdn.jsdelivr.net/npm/jquery/dist/jquery.min.js 29.7 KB 85.5 KB https://cdn.jsdelivr.net/npm/bootstrap@5.1.3/dist/js/bootstrap.bundle.min.js 22.0 KB 76.3 KB https://unpkg.com/bootstrap-table@1.21.2/dist/bootstrap-table.min.js 41.4 KB 132.7 KB https://unpkg.com/leaflet@1.9.3/dist/leaflet.js 41.8 KB 143.3 KB https://cdn.jsdelivr.net/npm/@gitlab/application-sdk-js@0.0.5/dist/gl-sdk.min.js 7.8 KB 21.5 KB
Avoid using incorrect mime types (mimeTypes)	The page has 1 misconfigured mime type.	99
Description: It's not a great idea to let browsers guess content types (content sniffing), in some cases it can actually be a security risk.
Offenders: https://allinbn.com/static/site.webmanifest
Make each CSS response small (optimalCssSize)	https://cdn.jsdelivr.net/npm/bootstrap@5.1.3/dist/css/bootstrap.min.css size is 21.6 kB (21627) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB.	90
Description: Make CSS responses small to fit into the magic number TCP window size of 14.5 KB. The browser can then download the CSS faster and that will make the page start rendering earlier.
Offenders: URL Transfer size Content size https://cdn.jsdelivr.net/npm/bootstrap@5.1.3/dist/css/bootstrap.min.css 21.1 KB 160.0 KB

Best practice advice (76)

Show/hide details

Title	Advice	Score
Meta description (metaDescription)	The page is missing a meta description.	0
Description: Use a page description to make the page more relevant to search engines.
Avoid too many third party requests (thirdParty)	The page do more requests to third party domains (10 requests and 197.4 kB) then first party (4 requests and 6.1 kB). The page transfer more bytes from third party domains (197.4 kB) then first party (6.1 kB). The regex .*allinbn.* was used to calculate first/third party requests.	0
Description: Do not load most of your content from third party URLs.
Avoid unnecessary headers (unnecessaryHeaders)	There are 4 responses that sets both a max-age and expires header. There are 14 responses that sets a server header.	82
Description: Do not send headers that you don't need. We look for p3p, cache-control and max-age, pragma, server and x-frame-options headers. Have a look at Andrew Betts - Headers for Hackers talk as a guide https://www.youtube.com/watch?v=k92ZbrY815c or read https://www.fastly.com/blog/headers-we-dont-want.
Offenders: https://allinbn.com/ https://allinbn.com/about/?next=/ https://cdn.jsdelivr.net/npm/bootstrap@5.1.3/dist/css/bootstrap.min.css https://cdn.jsdelivr.net/npm/bootstrap-icons@1.7.2/font/bootstrap-icons.css https://unpkg.com/bootstrap-table@1.21.2/dist/bootstrap-table.min.css https://unpkg.com/bootstrap-table@1.21.2/dist/bootstrap-table.min.css https://cdn.jsdelivr.net/npm/bootstrap-icons@1.10.3/font/bootstrap-icons.css https://unpkg.com/leaflet@1.9.3/dist/leaflet.css https://unpkg.com/leaflet@1.9.3/dist/leaflet.css https://cdn.jsdelivr.net/npm/jquery/dist/jquery.min.js https://cdn.jsdelivr.net/npm/bootstrap@5.1.3/dist/js/bootstrap.bundle.min.js https://unpkg.com/bootstrap-table@1.21.2/dist/bootstrap-table.min.js https://unpkg.com/bootstrap-table@1.21.2/dist/bootstrap-table.min.js https://unpkg.com/leaflet@1.9.3/dist/leaflet.js https://unpkg.com/leaflet@1.9.3/dist/leaflet.js https://cdn.jsdelivr.net/npm/@gitlab/application-sdk-js@0.0.5/dist/gl-sdk.min.js https://allinbn.com/static/site.webmanifest https://allinbn.com/static/favicon.ico

Privacy advice (91)

Show/hide details

Title	Advice	Score
Use a good Content-Security-Policy header to make sure you you avoid Cross Site Scripting (XSS) attacks. (contentSecurityPolicyHeader)	Set a Content-Security-Policy header to make sure you are not open for Cross Site Scripting (XSS) attacks. You can start with setting a Content-Security-Policy-Report-Only header, that will only report the violation, not stop the download.	0
Description: Content Security Policy is delivered via a HTTP response header, and defines approved sources of content that the browser may load. It can be an effective countermeasure to Cross Site Scripting (XSS) attacks and is also widely supported and usually easily deployed. https://scotthelme.co.uk/content-security-policy-an-introduction/.
Offenders: https://allinbn.com/about/?next=/
Do not share user data with third parties. (thirdPartyPrivacy)	The page has 71% requests that are 3rd party (10 requests with a size of 197.4 kB).	29
Description: Using third party requests shares user information with that third party. Please avoid that! The project https://github.com/patrickhulce/third-party-web is used to categorize first/third party requests.
Offenders: https://cdn.jsdelivr.net/npm/bootstrap@5.1.3/dist/css/bootstrap.min.css https://cdn.jsdelivr.net/npm/bootstrap-icons@1.7.2/font/bootstrap-icons.css https://unpkg.com/bootstrap-table@1.21.2/dist/bootstrap-table.min.css https://cdn.jsdelivr.net/npm/bootstrap-icons@1.10.3/font/bootstrap-icons.css https://unpkg.com/leaflet@1.9.3/dist/leaflet.css https://cdn.jsdelivr.net/npm/jquery/dist/jquery.min.js https://cdn.jsdelivr.net/npm/bootstrap@5.1.3/dist/js/bootstrap.bundle.min.js https://unpkg.com/bootstrap-table@1.21.2/dist/bootstrap-table.min.js https://unpkg.com/leaflet@1.9.3/dist/leaflet.js https://cdn.jsdelivr.net/npm/@gitlab/application-sdk-js@0.0.5/dist/gl-sdk.min.js

Page info

Page info
Title	AllInBN
Width	1350
Height	833
DOM elements	62
Avg DOM depth	4
Max DOM depth	9
Iframes	0
Script tags	6
Local storage	19 B
Session storage	0 b
Network Information API	4g

Technologies used to build the page.

Data collected using Wappalyzer version 6.10.66. With updated code from Webappanalyzer 2024-12-27. Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyzer find more information about technologies used.

Technology	Confidence	Category
Fly.io	100	PaaS
HSTS	100	Security
Cloudflare	100	CDN
HTTP/3	100	Miscellaneous

Data collected using Third Party Web 0.26.2

Cdn
JSDelivr CDN
Unpkg

Data from run 3

Visual Metrics

Browser Metrics

Largest Contentful Paint

When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.

Element type	P
Element/tag	<p></p>
Render time	364 ms
Element render delay	201 ms
TTFB	164 ms
Resource delay	0 ms
Resource load duration	0 ms
Load time	0 ms
Size (width*height)	74303
DOM path
div > p:eq(5)> div > p:eq(5)>

The largest contentful paint is highlighted in the image. If no element is highlighted the element was removed before the screenshot or the LCP API couldn't find the element.

Detected Cumulative Layout Shift

No layout shift detected.

Long Animation Frames

Read more about the Long Animation Frames API here here.

The top 10 longest animation frames entries

Server timings

There are no Server Timings.

Custom metrics collected through JavaScript

There are no custom configured scripts.

Extra metrics collected using scripting

There are no custom extra metrics from scripting.

PageXray

How the page is built.

Largest assets on the page (by transfer size)

Requests and sizes per content type

Data per domain

Expires and last modified statistics

Requests loaded after onLoad event

Included requests done after load event end.

Requests loaded after onContentLoad

Includes requests done after DOM content loaded.

Third party

Third party requests categorised by Third party web version 0.26.2.

Third party requests and tools

First party requests and sizes per content type

Calculated using .*allinbn.* (use --firstParty to configure).

Third party requests and sizes per content type