968 ms in total
92 ms
764 ms
112 ms
Click here to check amazing Core MyBlueprint content for Canada. Otherwise, check out these important facts you probably never knew about core.myblueprint.ca
Visit core.myblueprint.caWe analyzed Core.myblueprint.ca page load time and found that the first response time was 92 ms and then it took 876 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
core.myblueprint.ca performance score
name
value
score
weighting
Value25.9 s
0/100
10%
Value26.5 s
0/100
25%
Value25.9 s
0/100
10%
Value3,470 ms
2/100
30%
Value0.223
56/100
15%
Value30.8 s
0/100
10%
92 ms
186 ms
13 ms
27 ms
36 ms
Our browser made a total of 29 requests to load all elements on the main page. We found that 93% of them (27 requests) were addressed to the original Core.myblueprint.ca, 7% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (325 ms) belongs to the original domain Core.myblueprint.ca.
Page size can be reduced by 412.2 kB (68%)
604.1 kB
191.8 kB
In fact, the total size of Core.myblueprint.ca main page is 604.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 451.0 kB which makes up the majority of the site volume.
Potential reduce by 13.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 13.7 kB or 71% of the original size.
Potential reduce by 583 B
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. Core MyBlueprint images are well optimized though.
Potential reduce by 303.7 kB
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 303.7 kB or 67% of the original size.
Potential reduce by 94.2 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. Core.myblueprint.ca needs all CSS files to be minified and compressed as it can save up to 94.2 kB or 76% of the original size.
Number of requests can be reduced by 19 (70%)
27
8
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Core MyBlueprint. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
core.myblueprint.ca
92 ms
core.myblueprint.ca
186 ms
mybp-ui.css
13 ms
pnotify.css
27 ms
ui-structure.css
36 ms
jquery-ui.css
40 ms
ui-selectmenu.css
44 ms
qtip.css
51 ms
lodash.js
45 ms
core.js
68 ms
core-migrate.js
86 ms
ui-core.js
89 ms
Common_JS.en-CA.resx.axd
120 ms
GoogleAnalytics.js
66 ms
PreLogin.css
116 ms
LoginControls.css
117 ms
WebResource.axd
199 ms
ScriptResource.axd
117 ms
ScriptResource.axd
261 ms
ScriptResource.axd
223 ms
ScriptResource.axd
325 ms
ScriptResource.axd
135 ms
ga.js
60 ms
mybp.png
14 ms
__utm.gif
11 ms
ScriptResource.axd
116 ms
existing_icon.jpg
31 ms
shadowline.png
31 ms
newuser_icon.jpg
29 ms
core.myblueprint.ca accessibility score
ARIA
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.
Impact
Issue
[role] values are not valid
ARIA IDs are not unique
Names and labels
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.
Impact
Issue
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
core.myblueprint.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
core.myblueprint.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
robots.txt is not valid
Mobile Friendly
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/).
Impact
Issue
Document uses legible font sizes
N/A
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Core.myblueprint.ca can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Core.myblueprint.ca main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
core.myblueprint.ca
Open Graph description is not detected on the main page of Core MyBlueprint. 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: