1.5 sec in total
139 ms
857 ms
520 ms
Visit mbs.ed.cr now to see the best up-to-date Mbs content and also check out these interesting facts you probably never knew about mbs.ed.cr
Visit mbs.ed.crWe analyzed Mbs.ed.cr page load time and found that the first response time was 139 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
mbs.ed.cr performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value28.6 s
0/100
25%
Value4.7 s
69/100
10%
Value130 ms
96/100
30%
Value0
100/100
15%
Value8.0 s
42/100
10%
139 ms
75 ms
67 ms
68 ms
73 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 86% of them (66 requests) were addressed to the original Mbs.ed.cr, 12% (9 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (395 ms) belongs to the original domain Mbs.ed.cr.
Page size can be reduced by 226.0 kB (1%)
36.8 MB
36.6 MB
In fact, the total size of Mbs.ed.cr main page is 36.8 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. Only a small number of websites need less resources to load. Images take 36.3 MB which makes up the majority of the site volume.
Potential reduce by 51.1 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 51.1 kB or 81% of the original size.
Potential reduce by 100.2 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. Mbs images are well optimized though.
Potential reduce by 31.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 31.7 kB or 12% of the original size.
Potential reduce by 43.0 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. Mbs.ed.cr needs all CSS files to be minified and compressed as it can save up to 43.0 kB or 24% of the original size.
Number of requests can be reduced by 25 (38%)
65
40
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mbs. 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 14 to 1 for CSS and as a result speed up the page load time.
mbs.ed.cr
139 ms
common-skeleton.mind41d.css
75 ms
tooltip.min.css
67 ms
font-awesome.css
68 ms
elegant-font.css
73 ms
style.css
70 ms
page-builder.css
108 ms
rs6.css
121 ms
style-core.css
134 ms
kingster-style-custom.css
130 ms
css
33 ms
css
50 ms
owl.carousel.min.css
128 ms
bootstrap.min.css
125 ms
style.css
158 ms
logo%20blanco@2x-8.png
172 ms
Traditions.png
183 ms
pa.png
185 ms
profile.png
188 ms
students.png
190 ms
Faculty.png
206 ms
2.png
226 ms
Parents.png
237 ms
Library.png
239 ms
Handbook.png
237 ms
apply.png
293 ms
work.png
293 ms
menu.png
302 ms
email-decode.min.js
234 ms
jquery.js
287 ms
kingster-learnpress.js
296 ms
script.js
302 ms
page-builder.js
335 ms
effect.min.js
341 ms
script-core.js
364 ms
isotope.js
343 ms
jquery-3.3.1.min.js
332 ms
popper.min.js
340 ms
bootstrap.min.js
340 ms
owl.carousel.min.js
285 ms
main.js
305 ms
imgprincipal.jpg
295 ms
3.jpg
294 ms
4.jpg
286 ms
5.jpg
287 ms
1.jpg
299 ms
2.jpg
297 ms
3.jpg
350 ms
4.jpg
349 ms
5.jpg
354 ms
1.jpg
348 ms
6.jpeg
335 ms
3.jpg
325 ms
4.jpg
350 ms
5.jpg
353 ms
1.jpg
347 ms
2.jpg
357 ms
3.jpg
333 ms
4.jpg
390 ms
5.jpg
379 ms
logo-color.php
377 ms
mep.png
357 ms
ass.jpeg
320 ms
wold.png
317 ms
cor.png
363 ms
logo.png
372 ms
92zPtBhPNqw79Ij1E865zBUv7myjJQVG.ttf
47 ms
92zPtBhPNqw79Ij1E865zBUv7myRJQVG.ttf
55 ms
92zPtBhPNqw79Ij1E865zBUv7mz9JQVG.ttf
134 ms
92zPtBhPNqw79Ij1E865zBUv7mwjJQVG.ttf
134 ms
92zPtBhPNqw79Ij1E865zBUv7myjJAVG.ttf
135 ms
92zPtBhPNqw79Ij1E865zBUv7mx9IgVG.ttf
135 ms
92zPtBhPNqw79Ij1E865zBUv7mxEIgVG.ttf
136 ms
92zPtBhPNqw79Ij1E865zBUv7mwjIgVG.ttf
137 ms
92zPtBhPNqw79Ij1E865zBUv7mwKIgVG.ttf
135 ms
LeBeauneNew.ttf
395 ms
fontawesome-webfont3e6e3e6e.woff
373 ms
mbs.ed.cr accessibility score
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
Links do not have a discernible 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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
mbs.ed.cr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
mbs.ed.cr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mbs.ed.cr 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 Mbs.ed.cr 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.
mbs.ed.cr
Open Graph description is not detected on the main page of Mbs. 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: