Tools & Wizards About Us
instabuggy.ca screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

instabuggy.ca

Grocery Delivery from Local Stores in Toronto, Ottawa, Montreal, Vancouver, Calgary, Edmonton, Winnipeg, Regina, Saskatoon. Buggy Delivers Groceries, ...

Page Load Speed

6.9 sec in total

First Response

84 ms

Resources Loaded

3.6 sec

Page Rendered

3.3 sec

instabuggy.ca screenshot

About Website

Welcome to instabuggy.ca homepage info - get ready to check Insta Buggy best content right away, or after learning these important things about instabuggy.ca

Get your groceries delivered in as little as 1 hour by Buggy - National delivery service. Delivering groceries, alcohol, kitchen supplies, pharmacy, electronics, pets foods and more.

Visit instabuggy.ca

Key Findings

We analyzed Instabuggy.ca page load time and found that the first response time was 84 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

instabuggy.ca performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.0 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value12,640 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value25.4 s

0/100

10%

Network Requests Diagram

instabuggy.ca

84 ms

www.inabuggy.com

304 ms

buggy.ca

595 ms

css

44 ms

styles.css

400 ms

Our browser made a total of 154 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Instabuggy.ca, 74% (114 requests) were made to Dwl4u4j54pgrl.cloudfront.net and 16% (25 requests) were made to Buggy.ca. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Buggy.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 712.6 kB (27%)

Content Size

2.7 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Instabuggy.ca main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 577.9 kB

  • Original 879.3 kB
  • After minification 837.7 kB
  • After compression 301.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. 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 577.9 kB or 66% of the original size.

Image Optimization

-8%

Potential reduce by 134.5 kB

  • Original 1.7 MB
  • After minification 1.6 MB

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. Insta Buggy images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 97 B

  • Original 33.6 kB
  • After minification 33.5 kB
  • After compression 33.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 59 B

  • Original 71.0 kB
  • After minification 71.0 kB
  • After compression 71.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. Instabuggy.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (9%)

Requests Now

140

After Optimization

128

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Insta 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 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

instabuggy.ca

instabuggy.ca

84 ms

www.inabuggy.com

www.inabuggy.com

304 ms

buggy.ca

buggy.ca

595 ms

css

css

44 ms

styles.css

styles.css

400 ms

scripts.js

scripts.js

461 ms

lazyload.min.js

lazyload.min.js

58 ms

test.js

test.js

200 ms

js

js

62 ms

css2

css2

17 ms

120361.ct.js

120361.ct.js

399 ms

fbevents.js

fbevents.js

289 ms

buggy.png

buggy.png

443 ms

favicon-96x96.png

favicon-96x96.png

278 ms

googleplay.png

googleplay.png

277 ms

appstore.png

appstore.png

276 ms

translation.svg

translation.svg

402 ms

translation_white.svg

translation_white.svg

388 ms

hb1.png

hb1.png

388 ms

hb2.png

hb2.png

400 ms

hb3.png

hb3.png

430 ms

eb1.png

eb1.png

423 ms

eb2.png

eb2.png

422 ms

eb3.png

eb3.png

422 ms

buggystore.png

buggystore.png

420 ms

1.svg

1.svg

487 ms

7.svg

7.svg

494 ms

8.svg

8.svg

491 ms

10.svg

10.svg

519 ms

11.svg

11.svg

532 ms

12.svg

12.svg

507 ms

14.svg

14.svg

551 ms

15.svg

15.svg

564 ms

16.svg

16.svg

553 ms

24.svg

24.svg

543 ms

25.svg

25.svg

560 ms

27.svg

27.svg

539 ms

36.svg

36.svg

580 ms

50.svg

50.svg

584 ms

52.svg

52.svg

678 ms

53.svg

53.svg

687 ms

55.svg

55.svg

638 ms

56.svg

56.svg

683 ms

80.svg

80.svg

637 ms

83.svg

83.svg

688 ms

84.svg

84.svg

729 ms

85.svg

85.svg

719 ms

96.svg

96.svg

731 ms

103.svg

103.svg

712 ms

110.svg

110.svg

715 ms

129.svg

129.svg

782 ms

video.jpg

video.jpg

584 ms

yplay.png

yplay.png

570 ms

hp-banner-xl.png

hp-banner-xl.png

576 ms

appstore.png

appstore.png

429 ms

playstore.png

playstore.png

530 ms

phone-cart.png

phone-cart.png

1136 ms

analytics.js

analytics.js

461 ms

Omnes-Regular.woff

Omnes-Regular.woff

1003 ms

Omnes-Medium.woff

Omnes-Medium.woff

880 ms

Omnes-Light.woff

Omnes-Light.woff

960 ms

Omnes-SemiBold.woff

Omnes-SemiBold.woff

1015 ms

Omnes-Bold.woff

Omnes-Bold.woff

677 ms

Omnes-SemiBoldItalic.woff

Omnes-SemiBoldItalic.woff

966 ms

Omnes-BoldItalic.woff

Omnes-BoldItalic.woff

1022 ms

Omnes-MedItalic.woff

Omnes-MedItalic.woff

1031 ms

Omnes-Italic.woff

Omnes-Italic.woff

1000 ms

OmnesLight-Italic.woff

OmnesLight-Italic.woff

1031 ms

buggyforms.woff

buggyforms.woff

998 ms

clackers.data

clackers.data

963 ms

141786436518339

141786436518339

92 ms

1.svg

1.svg

413 ms

7.svg

7.svg

380 ms

8.svg

8.svg

422 ms

jsp

jsp

546 ms

10.svg

10.svg

384 ms

11.svg

11.svg

387 ms

12.svg

12.svg

474 ms

14.svg

14.svg

462 ms

15.svg

15.svg

437 ms

16.svg

16.svg

449 ms

24.svg

24.svg

389 ms

25.svg

25.svg

375 ms

27.svg

27.svg

415 ms

36.svg

36.svg

387 ms

50.svg

50.svg

462 ms

52.svg

52.svg

372 ms

53.svg

53.svg

365 ms

55.svg

55.svg

369 ms

56.svg

56.svg

370 ms

80.svg

80.svg

386 ms

83.svg

83.svg

375 ms

84.svg

84.svg

349 ms

85.svg

85.svg

364 ms

96.svg

96.svg

367 ms

collect

collect

271 ms

collect

collect

101 ms

103.svg

103.svg

344 ms

110.svg

110.svg

297 ms

129.svg

129.svg

277 ms

130.svg

130.svg

285 ms

132.svg

132.svg

302 ms

151.svg

151.svg

303 ms

153.svg

153.svg

293 ms

155.svg

155.svg

284 ms

156.svg

156.svg

277 ms

157.svg

157.svg

430 ms

158.svg

158.svg

304 ms

33.svg

33.svg

304 ms

35.svg

35.svg

272 ms

41.svg

41.svg

242 ms

59.svg

59.svg

280 ms

61.svg

61.svg

260 ms

152.svg

152.svg

278 ms

77.svg

77.svg

266 ms

130.svg

130.svg

312 ms

132.svg

132.svg

314 ms

151.svg

151.svg

314 ms

153.svg

153.svg

310 ms

collect

collect

502 ms

155.svg

155.svg

309 ms

156.svg

156.svg

303 ms

157.svg

157.svg

297 ms

158.svg

158.svg

294 ms

33.svg

33.svg

294 ms

35.svg

35.svg

294 ms

41.svg

41.svg

292 ms

59.svg

59.svg

292 ms

61.svg

61.svg

297 ms

152.svg

152.svg

298 ms

77.svg

77.svg

294 ms

visa.jpg

visa.jpg

294 ms

master.jpg

master.jpg

290 ms

amex.jpg

amex.jpg

286 ms

discover.jpg

discover.jpg

283 ms

interac.jpg

interac.jpg

266 ms

fb.png

fb.png

264 ms

in.png

in.png

261 ms

ig.png

ig.png

260 ms

tw.png

tw.png

255 ms

bag.png

bag.png

252 ms

fruits.png

fruits.png

230 ms

dairy.png

dairy.png

226 ms

meat.png

meat.png

223 ms

snacks.png

snacks.png

208 ms

frozen.png

frozen.png

205 ms

pantry.png

pantry.png

202 ms

beverages.png

beverages.png

185 ms

baby.png

baby.png

180 ms

pet.png

pet.png

178 ms

household.png

household.png

179 ms

health.png

health.png

191 ms

alcohol.png

alcohol.png

185 ms

cs

cs

37 ms

Accessibility Review

instabuggy.ca accessibility score

57

Accessibility Issues

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

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.

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

instabuggy.ca best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

instabuggy.ca SEO score

90

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

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

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 Instabuggy.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 Instabuggy.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

instabuggy.ca

Open Graph description is not detected on the main page of Insta 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: