2.7 sec in total
149 ms
2.2 sec
440 ms
Click here to check amazing Ina Buggy content for Canada. Otherwise, check out these important facts you probably never knew about inabuggy.com
15 minute delivery in Toronto and London, offering groceries, alcohol, pharmacy and personal wellness products from your favourite brands. Delivering groceries, alcohol, kitchen supplies, pharmacy, el...
Visit inabuggy.comWe analyzed Inabuggy.com page load time and found that the first response time was 149 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
inabuggy.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value6.8 s
7/100
25%
Value4.4 s
75/100
10%
Value590 ms
50/100
30%
Value0.005
100/100
15%
Value9.9 s
27/100
10%
149 ms
652 ms
43 ms
360 ms
474 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Inabuggy.com, 86% (44 requests) were made to Buggy.ca and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (915 ms) relates to the external source Buggy.ca.
Page size can be reduced by 340.4 kB (20%)
1.7 MB
1.4 MB
In fact, the total size of Inabuggy.com main page is 1.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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 99.3 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 23.9 kB, which is 19% 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 99.3 kB or 79% of the original size.
Potential reduce by 241.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. Obviously, Ina Buggy needs image optimization as it can save up to 241.0 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 58 B
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. Inabuggy.com has all CSS files already compressed.
Number of requests can be reduced by 5 (13%)
38
33
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ina Buggy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
inabuggy.com
149 ms
buggy.ca
652 ms
css
43 ms
styles.css
360 ms
scripts.js
474 ms
lazyload.min.js
32 ms
test.js
179 ms
js
66 ms
css2
12 ms
fbevents.js
124 ms
favicon-96x96.png
121 ms
googleplay.png
122 ms
appstore.png
120 ms
buggy-black.png
729 ms
translation.svg
398 ms
translation_white.svg
396 ms
hb1.png
453 ms
hb2-1.png
570 ms
hb2.png
572 ms
hb3.png
572 ms
eb1.png
515 ms
eb2.png
571 ms
eb3.png
576 ms
buggystore.png
631 ms
visa.jpg
630 ms
master.jpg
633 ms
amex.jpg
633 ms
discover.jpg
635 ms
interac.jpg
691 ms
sh.png
690 ms
fb.png
690 ms
in.png
691 ms
ig.png
694 ms
tw.png
749 ms
bag.png
912 ms
video.jpg
914 ms
yplay.png
683 ms
phone-cart.png
915 ms
Omnes-Regular.woff
649 ms
Omnes-Medium.woff
729 ms
Omnes-Light.woff
671 ms
Omnes-SemiBold.woff
766 ms
Omnes-Bold.woff
789 ms
Omnes-SemiBoldItalic.woff
852 ms
Omnes-BoldItalic.woff
834 ms
Omnes-MedItalic.woff
861 ms
Omnes-Italic.woff
904 ms
OmnesLight-Italic.woff
861 ms
buggyforms.woff
812 ms
events.js
37 ms
clackers.data
696 ms
inabuggy.com 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
Image elements do not have [alt] attributes
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.
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.
inabuggy.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
General
Impact
Issue
Detected JavaScript libraries
inabuggy.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inabuggy.com 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 Inabuggy.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.
inabuggy.com
Open Graph description is not detected on the main page of Ina Buggy. 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: