4.4 sec in total
534 ms
3.4 sec
526 ms
Welcome to foscam.ca homepage info - get ready to check Foscam best content for Canada right away, or after learning these important things about foscam.ca
foscam camera
Visit foscam.caWe analyzed Foscam.ca page load time and found that the first response time was 534 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
foscam.ca performance score
534 ms
83 ms
61 ms
38 ms
38 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 82% of them (64 requests) were addressed to the original Foscam.ca, 5% (4 requests) were made to Google-analytics.com and 5% (4 requests) were made to Secure.livechatinc.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Foscam.ca.
Page size can be reduced by 1.2 MB (31%)
4.1 MB
2.8 MB
In fact, the total size of Foscam.ca main page is 4.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 2.6 MB which makes up the majority of the site volume.
Potential reduce by 26.6 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 4.6 kB, which is 14% 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 26.6 kB or 80% of the original size.
Potential reduce by 195.4 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. Foscam images are well optimized though.
Potential reduce by 895.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 895.4 kB or 73% of the original size.
Potential reduce by 124.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. Foscam.ca needs all CSS files to be minified and compressed as it can save up to 124.7 kB or 85% of the original size.
Number of requests can be reduced by 31 (42%)
74
43
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foscam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
foscam.ca
534 ms
58290b6f1a18d87ec3cd96a5e9d5911d.css
83 ms
prototype.js
61 ms
ccard.js
38 ms
validation.js
38 ms
builder.js
40 ms
effects.js
41 ms
dragdrop.js
49 ms
controls.js
50 ms
slider.js
51 ms
js.js
56 ms
form.js
63 ms
menu.js
64 ms
translate.js
66 ms
cookies.js
69 ms
ddmenu.js
72 ms
modernizr.js
76 ms
css
24 ms
jquery-1.10.2.min.js
142 ms
libs.js
153 ms
main.js
140 ms
ga.js
104 ms
analytics.js
104 ms
bg.jpg
139 ms
icon_sprite.png
141 ms
us.gif
139 ms
ca.gif
140 ms
gb.gif
142 ms
eu.gif
141 ms
logo.png
143 ms
9821w_-_front_3_2.png
144 ms
foscam_fi9805w_1__2.png
146 ms
9831wb_-_front_2.png
145 ms
foscam_fi9805e_1.png
144 ms
9826-front-png_5.png
144 ms
fi9828w_2.png
147 ms
fhc52-png_1_.png
146 ms
9826-front-png_12.png
148 ms
cloud_storage.jpg
146 ms
3501main.jpg
150 ms
ac1080.jpg
147 ms
fr305.jpg
149 ms
61x7lY-xvWL._SL1500_.png
151 ms
banner1.jpg
148 ms
category_thumbnail_3.png
181 ms
category_thumbnail_1.png
152 ms
foscam_fi9805w_1__1_2.png
150 ms
fi9828w_5.png
175 ms
category_thumbnail_5.png
162 ms
fi9804w_1.png
152 ms
910wb_-_front_1.png
163 ms
fi8918w.foscam.us_1.png
168 ms
8905_1_1.png
163 ms
fbm3502_2_1.png
166 ms
router_img.png
167 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
131 ms
goole_logo.png
165 ms
app_logo.png
162 ms
tracking.js
120 ms
banner2.jpg
92 ms
parameter_img.png
108 ms
__utm.gif
38 ms
collect
61 ms
collect
29 ms
banner3.jpg
48 ms
in_img.png
47 ms
twit_img.png
48 ms
goo_img.png
58 ms
face_img.png
58 ms
bkg_main1.gif
2532 ms
bkg_main2.gif
1404 ms
script_data.js
87 ms
localization.en.0.3632191afe35222a6b78c04d457adc0d_fd6509245f8cd00ca269b25e864fcb3d.js
42 ms
ping
74 ms
sprite.20111206.png
31 ms
open_chat.cgi
71 ms
embedded.20160318100705.js
115 ms
10fca1569bf3067882c979652378c2b2.css
17 ms
foscam.ca SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foscam.ca 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 Foscam.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.
foscam.ca
Open Graph description is not detected on the main page of Foscam. 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: