Tools & Wizards About Us
arlo.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

arlo.com

Arlo Security Cameras System & Video Doorbells | Up to 25% Off

Page Load Speed

2 sec in total

First Response

245 ms

Resources Loaded

1.5 sec

Page Rendered

279 ms

arlo.com screenshot

About Website

Welcome to arlo.com homepage info - get ready to check Arlo best content for United States right away, or after learning these important things about arlo.com

Protect your everything with Arlo's wifi-enabled wired & wireless security cameras, video doorbells & home security system. Available in HD, 2K or 4K.

Visit arlo.com

Key Findings

We analyzed Arlo.com page load time and found that the first response time was 245 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

arlo.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value41.3 s

0/100

25%

SI (Speed Index)

Value26.5 s

0/100

10%

TBT (Total Blocking Time)

Value6,440 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.2

62/100

15%

TTI (Time to Interactive)

Value60.8 s

0/100

10%

Network Requests Diagram

245 ms

main.js

137 ms

jquery.zoom.min.js

53 ms

productTile.js

84 ms

homepage.js

53 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 78% of them (63 requests) were addressed to the original Arlo.com, 4% (3 requests) were made to Edqprofservus.blob.core.windows.net and 2% (2 requests) were made to Nova.collect.igodigital.com. The less responsive or slowest element that took the longest time to load (714 ms) belongs to the original domain Arlo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 311.2 kB (10%)

Content Size

3.1 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Arlo.com main page is 3.1 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.9 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 153.5 kB

  • Original 180.6 kB
  • After minification 180.4 kB
  • After compression 27.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 153.5 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 90.9 kB

  • Original 1.9 MB
  • After minification 1.8 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. Arlo images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 61.0 kB

  • Original 894.2 kB
  • After minification 891.9 kB
  • After compression 833.2 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

-6%

Potential reduce by 5.8 kB

  • Original 89.6 kB
  • After minification 88.2 kB
  • After compression 83.8 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. Arlo.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (61%)

Requests Now

75

After Optimization

29

  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Arlo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

245 ms

main.js

main.js

137 ms

jquery.zoom.min.js

jquery.zoom.min.js

53 ms

productTile.js

productTile.js

84 ms

homepage.js

homepage.js

53 ms

cjclickidcookie.js

cjclickidcookie.js

52 ms

affirm.js

affirm.js

110 ms

select2.min.css

select2.min.css

131 ms

global.css

global.css

51 ms

homePage.css

homePage.css

123 ms

edq.js

edq.js

137 ms

global-intuitive-unicorn.css

global-intuitive-unicorn.css

134 ms

pro-web.css

pro-web.css

136 ms

accessibe.js

accessibe.js

136 ms

collect.js

collect.js

106 ms

script-tag.js

script-tag.js

99 ms

converseapps-bot.js

converseapps-bot.js

144 ms

dwanalytics-22.2.js

dwanalytics-22.2.js

129 ms

dwac-21.7.js

dwac-21.7.js

126 ms

gretel.min.js

gretel.min.js

102 ms

applepay.js

applepay.js

128 ms

css

css

104 ms

gtm.js

gtm.js

303 ms

j.php

j.php

313 ms

acsb.js

acsb.js

298 ms

logo.svg

logo.svg

241 ms

search.png

search.png

219 ms

cart.png

cart.png

219 ms

security-system-2-sensor-phone.png

security-system-2-sensor-phone.png

227 ms

bundle-builder.png

bundle-builder.png

223 ms

essential-xl-v2-right.png

essential-xl-v2-right.png

225 ms

Pro5_Pro4_White_Right.png

Pro5_Pro4_White_Right.png

222 ms

essential-v2-right.png

essential-v2-right.png

234 ms

Ultra_UltraV2_White_Right.png

Ultra_UltraV2_White_Right.png

577 ms

essential-indoor-v2-right.png

essential-indoor-v2-right.png

580 ms

04%20-%20GO%202%20LTE%20-%20Wireless%20Camera.png

04%20-%20GO%202%20LTE%20-%20Wireless%20Camera.png

578 ms

arlo-doorbell-right.png

arlo-doorbell-right.png

580 ms

07%20-%20Pro%203%20Floodlight%20-%20Wireless%20Camera.png

07%20-%20Pro%203%20Floodlight%20-%20Wireless%20Camera.png

609 ms

Arlo%20Secure.svg

Arlo%20Secure.svg

580 ms

Arlo%20Total%20Security.svg

Arlo%20Total%20Security.svg

606 ms

Arlo%20Safe.svg

Arlo%20Safe.svg

604 ms

btn-arrow-arlo-light-blue.svg

btn-arrow-arlo-light-blue.svg

603 ms

Arlo-Buy-More-Save-More-2024-Mobile.jpg

Arlo-Buy-More-Save-More-2024-Mobile.jpg

607 ms

btn-arrow-arlo-blue.svg

btn-arrow-arlo-blue.svg

605 ms

Arlo-Starter-Kits-50-Percent-Off-2024-Mobile.jpg

Arlo-Starter-Kits-50-Percent-Off-2024-Mobile.jpg

666 ms

btn-arrow-white.svg

btn-arrow-white.svg

660 ms

au.svg

au.svg

660 ms

be.svg

be.svg

663 ms

ca.svg

ca.svg

662 ms

dk.svg

dk.svg

664 ms

de.svg

de.svg

667 ms

es.svg

es.svg

668 ms

fi.svg

fi.svg

669 ms

fr.svg

fr.svg

671 ms

hk.svg

hk.svg

672 ms

it.svg

it.svg

675 ms

jp.svg

jp.svg

673 ms

nl.svg

nl.svg

671 ms

nz.svg

nz.svg

674 ms

no.svg

no.svg

714 ms

aa.svg

aa.svg

712 ms

gr

gr

513 ms

b35c33f5acde319a25521b385941365f.js

b35c33f5acde319a25521b385941365f.js

448 ms

track_cart

track_cart

414 ms

track_page_view

track_page_view

412 ms

SuisseIntl-Medium.ttf

SuisseIntl-Medium.ttf

531 ms

SuisseIntl-Regular.ttf

SuisseIntl-Regular.ttf

508 ms

acsb.js

acsb.js

448 ms

SuisseIntl-SemiBold.ttf

SuisseIntl-SemiBold.ttf

576 ms

pl.svg

pl.svg

496 ms

ch.svg

ch.svg

497 ms

sg.svg

sg.svg

496 ms

se.svg

se.svg

491 ms

gb.svg

gb.svg

493 ms

asia-en.svg

asia-en.svg

151 ms

eu.svg

eu.svg

216 ms

us.svg

us.svg

219 ms

privacy-center-icon.png

privacy-center-icon.png

219 ms

ajax-loader.gif

ajax-loader.gif

204 ms

btn-arrow-white.svg

btn-arrow-white.svg

198 ms

undefined

undefined

189 ms

Accessibility Review

arlo.com accessibility score

89

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

arlo.com best practices score

67

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

arlo.com SEO score

75

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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

Social Sharing Optimization

arlo.com

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