Access orl.bc.ca. Okanagan Regional Library | Kelowna & Okanagan Public Libraries

name

value

score

weighting

FCP (First Contentful Paint)

Value34.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value37.7 s

0/100

25%

SI (Speed Index)

Value34.3 s

0/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.116

85/100

15%

TTI (Time to Interactive)

Value39.2 s

0/100

10%

orl.bc.ca

157 ms

orl.bc.ca

609 ms

gtm.js

73 ms

core.css

371 ms

css

47 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 80% of them (70 requests) were addressed to the original Orl.bc.ca, 5% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Orl.bc.ca.

Content Size

6.7 MB

After Optimization

2.5 MB

In fact, the total size of Orl.bc.ca main page is 6.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 341.0 kB

Original 374.4 kB
After minification 279.5 kB
After compression 33.4 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 94.9 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 341.0 kB or 91% of the original size.

Image Optimization

-7%

Potential reduce by 74.5 kB

Original 998.9 kB
After minification 924.3 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Orl images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 3.7 MB

Original 5.2 MB
After minification 5.1 MB
After compression 1.5 MB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 3.7 MB or 71% of the original size.

CSS Optimization

-58%

Potential reduce by 54.6 kB

Original 94.5 kB
After minification 91.3 kB
After compression 39.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Orl.bc.ca needs all CSS files to be minified and compressed as it can save up to 54.6 kB or 58% of the original size.

Requests Now

After Optimization

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role] values are not valid

High

[aria-*] attributes do not have valid values

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orl.bc.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Orl.bc.ca main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

orl.bc.ca

Open Graph description is not detected on the main page of Orl. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

Report Summary

Performance

Accessibility

Best Practices

SEO

Okanagan Regional Library | Kelowna & Okanagan Public Libraries

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

orl.bc.ca

orl.bc.ca

gtm.js

core.css

css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

orl.bc.ca

orl.bc.ca

gtm.js

core.css

css

main.css

animate.css

content.css

modernizr.min.js

jquery.min.js

fastclick.js

fd6a6fb2ea.js

slick.min.js

isotope.pkgd.min.js

jquery.infinitescroll.min.js

site-functions.js

Telerik.Web.UI.WebResource.axd

login.min.css

font-awesome.css

Treeview.css

Window.css

home.css

WebResource.axd

Telerik.Web.UI.WebResource.axd

ScriptResource.axd

Telerik.Web.UI.WebResource.axd

ScriptResource.axd

ScriptResource.axd

Telerik.Web.UI.WebResource.axd

ScriptResource.axd

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

analytics.js

collect

collect

js

eventListWidget.css

eventsxml.aspx

7325912.js

404

404

404

404