5.5 sec in total
1.1 sec
4 sec
388 ms
Visit webboxcr.com now to see the best up-to-date Web Box Cr content for Costa Rica and also check out these interesting facts you probably never knew about webboxcr.com
Visit webboxcr.comWe analyzed Webboxcr.com page load time and found that the first response time was 1.1 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
webboxcr.com performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value5.9 s
14/100
25%
Value6.2 s
43/100
10%
Value290 ms
80/100
30%
Value0.057
98/100
15%
Value10.0 s
26/100
10%
1081 ms
141 ms
143 ms
144 ms
156 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 79% of them (56 requests) were addressed to the original Webboxcr.com, 6% (4 requests) were made to Translate.googleapis.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Mrrabbit.cr.
Page size can be reduced by 834.9 kB (23%)
3.7 MB
2.9 MB
In fact, the total size of Webboxcr.com main page is 3.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. 45% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 19.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 19.7 kB or 79% of the original size.
Potential reduce by 62.0 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. Web Box Cr images are well optimized though.
Potential reduce by 404.4 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 404.4 kB or 60% of the original size.
Potential reduce by 348.7 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. Webboxcr.com needs all CSS files to be minified and compressed as it can save up to 348.7 kB or 85% of the original size.
Number of requests can be reduced by 49 (72%)
68
19
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Web Box Cr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
webboxcr.com
1081 ms
system.base.css
141 ms
system.menus.css
143 ms
system.messages.css
144 ms
system.theme.css
156 ms
comment.css
163 ms
field.css
164 ms
node.css
207 ms
search.css
213 ms
user.css
214 ms
views.css
234 ms
colorbox_style.css
243 ms
ctools.css
244 ms
default.css
276 ms
nivo-slider.css
283 ms
bootstrap.css
566 ms
bootstrap-responsive.css
390 ms
animate.css
487 ms
font-awesome.css
405 ms
style.css
548 ms
media.css
353 ms
jcarousel.css
426 ms
docs.css
470 ms
jquery.min.js
729 ms
jquery.once.js
497 ms
drupal.js
554 ms
es_0JT2b_3epsbDvhy34PA06_Un1r3YaDM9ZhA6Fhp-Eq4.js
582 ms
jquery.colorbox-min.js
583 ms
colorbox.js
614 ms
colorbox_style.js
631 ms
js
34 ms
google_map_field_node_display.js
632 ms
googleanalytics.js
646 ms
nivo_slider.js
637 ms
jquery.nivo.slider.pack.js
683 ms
jquery.js
1110 ms
bootstrap.min.js
704 ms
element.js
55 ms
bootstrap.js
842 ms
custom.js
599 ms
css
39 ms
317 ms
logoFront.png
1833 ms
top_header.png
100 ms
logo%20webbox%20final-01.png
213 ms
menu-leaf.png
91 ms
menu_hover.png
91 ms
9.png
773 ms
loading.gif
92 ms
banner1%20%282%29.png
450 ms
banner3.png
589 ms
banner2.png
566 ms
banner4.png
650 ms
banner5%20%281%29.png
904 ms
1112_ShoppingCart_Article.jpg
527 ms
3.png
611 ms
avion%20600x350.jpg
637 ms
4.png
679 ms
translateelement.css
74 ms
main.js
149 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
35 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
43 ms
ga.js
71 ms
webboxcr.com
1224 ms
arrows.png
517 ms
bullets.png
521 ms
element_main.js
40 ms
__utm.gif
14 ms
translate_24dp.png
56 ms
l
51 ms
googlelogo_color_42x16dp.png
42 ms
webboxcr.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
webboxcr.com 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
webboxcr.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webboxcr.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Webboxcr.com 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.
webboxcr.com
Open Graph description is not detected on the main page of Web Box Cr. 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: