13.9 sec in total
176 ms
13.6 sec
155 ms
Click here to check amazing Funnybunnyphoto content. Otherwise, check out these important facts you probably never knew about funnybunnyphoto.com
Funny Bunny Photography is a San Francisco Bay Area studio specializing in geek wedding photography - be a superhero on your wedding day and be yourself!
Visit funnybunnyphoto.comWe analyzed Funnybunnyphoto.com page load time and found that the first response time was 176 ms and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
funnybunnyphoto.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value6.7 s
7/100
25%
Value8.3 s
19/100
10%
Value130 ms
96/100
30%
Value0.191
64/100
15%
Value5.5 s
71/100
10%
176 ms
1181 ms
180 ms
186 ms
186 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 28% of them (42 requests) were addressed to the original Funnybunnyphoto.com, 28% (42 requests) were made to I0.wp.com and 22% (33 requests) were made to I1.wp.com. The less responsive or slowest element that took the longest time to load (11.6 sec) relates to the external source I1.wp.com.
Page size can be reduced by 713.9 kB (7%)
10.8 MB
10.1 MB
In fact, the total size of Funnybunnyphoto.com main page is 10.8 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. 75% 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 9.9 MB which makes up the majority of the site volume.
Potential reduce by 500.5 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 500.5 kB or 94% of the original size.
Potential reduce by 42.7 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. Funnybunnyphoto images are well optimized though.
Potential reduce by 155.7 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 155.7 kB or 53% of the original size.
Potential reduce by 15.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. Funnybunnyphoto.com needs all CSS files to be minified and compressed as it can save up to 15.0 kB or 30% of the original size.
Number of requests can be reduced by 34 (24%)
144
110
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funnybunnyphoto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
funnybunnyphoto.com
176 ms
funnybunnyphoto.com
1181 ms
style.css
180 ms
skeleton.css
186 ms
layout.css
186 ms
style.min.css
214 ms
styles.css
368 ms
meteor-slides.css
232 ms
css
29 ms
jquery-ui.min.css
376 ms
jetpack.css
310 ms
modernizr.custom.40618.js
251 ms
jquery.min.js
313 ms
jquery-migrate.min.js
301 ms
jquery.cycle.all.js
397 ms
jquery.metadata.v2.js
367 ms
jquery.touchwipe.1.1.1.js
385 ms
slideshow.js
400 ms
pinit.js
451 ms
comment-reply.min.js
267 ms
photon.min.js
287 ms
wp-polyfill.min.js
335 ms
index.js
286 ms
jquery.sonar.min.js
332 ms
lazy-load.js
361 ms
core.min.js
362 ms
datepicker.min.js
362 ms
html5-fallback.js
361 ms
wp-embed.min.js
396 ms
e-202433.js
12 ms
wp-emoji-release.min.js
356 ms
bg.jpg
311 ms
2015Weddings-FBP_0001.jpg
555 ms
header.png
226 ms
border1.png
171 ms
border2.png
170 ms
1x1.trans.gif
217 ms
footer.png
469 ms
border3.png
234 ms
pinit_fg_en_rect_red_28.png
19 ms
4UaHrEJCrhhnVA3DgluA96rp4Q.woff
19 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
23 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff
30 ms
pinit_main.js
12 ms
wp-polyfill-fetch.min.js
120 ms
wp-polyfill-dom-rect.min.js
168 ms
wp-polyfill-url.min.js
178 ms
wp-polyfill-formdata.min.js
186 ms
wp-polyfill-element-closest.min.js
186 ms
wp-polyfill-object-fit.min.js
234 ms
1f642.svg
106 ms
2015Weddings-FBP_0002.jpg
127 ms
2015Weddings-FBP_0003.jpg
175 ms
2015Weddings-FBP_0009.jpg
600 ms
2015Weddings-FBP_0010.jpg
450 ms
2015Weddings-FBP_0011.jpg
566 ms
2015Weddings-FBP_0017.jpg
579 ms
2015Weddings-FBP_0021.jpg
569 ms
2015Weddings-FBP_0022.jpg
568 ms
2015Weddings-FBP_0026.jpg
864 ms
2015Weddings-FBP_0027.jpg
1070 ms
2015Weddings-FBP_0034.jpg
1018 ms
2015Weddings-FBP_0035.jpg
1051 ms
2015Weddings-FBP_0036.jpg
1099 ms
2015Weddings-FBP_0037.jpg
1123 ms
2015Weddings-FBP_0044.jpg
1265 ms
2015Weddings-FBP_0052.jpg
6358 ms
2015Weddings-FBP_0054.jpg
1552 ms
2015Weddings-FBP_0055.jpg
1531 ms
2015Weddings-FBP_0059.jpg
1596 ms
2015Weddings-FBP_0062.jpg
1610 ms
2015Weddings-FBP_0066.jpg
1756 ms
2015Weddings-FBP_0067.jpg
2030 ms
2015Weddings-FBP_0068.jpg
11581 ms
2015Weddings-FBP_0073.jpg
2090 ms
2015Weddings-FBP_0076.jpg
2089 ms
2015Weddings-FBP_0078.jpg
2276 ms
2015Weddings-FBP_0079.jpg
2478 ms
2015Weddings-FBP_0081.jpg
2577 ms
2015Weddings-FBP_0084.jpg
2547 ms
2015Weddings-FBP_0086.jpg
2771 ms
2015Weddings-FBP_0087.jpg
2499 ms
2015Weddings-FBP_0089.jpg
3078 ms
2015Weddings-FBP_0093.jpg
3584 ms
2015Weddings-FBP_0097.jpg
3144 ms
2015Weddings-FBP_0004.jpg
508 ms
2015Weddings-FBP_0007.jpg
3220 ms
2015Weddings-FBP_0013.jpg
603 ms
2015Weddings-FBP_0016.jpg
535 ms
2015Weddings-FBP_0018.jpg
632 ms
2015Weddings-FBP_0019.jpg
684 ms
2015Weddings-FBP_0020.jpg
4522 ms
2015Weddings-FBP_0028.jpg
988 ms
2015Weddings-FBP_0031.jpg
1088 ms
2015Weddings-FBP_0033.jpg
1092 ms
2015Weddings-FBP_0038.jpg
1161 ms
2015Weddings-FBP_0042.jpg
1459 ms
2015Weddings-FBP_0045.jpg
5396 ms
2015Weddings-FBP_0046.jpg
1541 ms
2015Weddings-FBP_0051.jpg
1607 ms
2015Weddings-FBP_0057.jpg
1935 ms
2015Weddings-FBP_0060.jpg
1560 ms
2015Weddings-FBP_0071.jpg
2033 ms
2015Weddings-FBP_0072.jpg
2132 ms
2015Weddings-FBP_0083.jpg
2466 ms
2015Weddings-FBP_0085.jpg
2567 ms
2015Weddings-FBP_0088.jpg
2537 ms
2015Weddings-FBP_0095.jpg
2972 ms
2015Weddings-FBP_0099.jpg
3115 ms
2015Weddings-FBP_0100.jpg
2587 ms
2015Weddings-FBP_0005.jpg
549 ms
2015Weddings-FBP_0006.jpg
574 ms
2015Weddings-FBP_0008.jpg
576 ms
2015Weddings-FBP_0012.jpg
522 ms
2015Weddings-FBP_0014.jpg
542 ms
2015Weddings-FBP_0015.jpg
570 ms
2015Weddings-FBP_0023.jpg
1044 ms
2015Weddings-FBP_0024.jpg
984 ms
2015Weddings-FBP_0025.jpg
10558 ms
2015Weddings-FBP_0029.jpg
1136 ms
2015Weddings-FBP_0030.jpg
1050 ms
2015Weddings-FBP_0032.jpg
1056 ms
2015Weddings-FBP_0039.jpg
1493 ms
2015Weddings-FBP_0040.jpg
6220 ms
2015Weddings-FBP_0041.jpg
1535 ms
2015Weddings-FBP_0043.jpg
7094 ms
2015Weddings-FBP_0047.jpg
5931 ms
2015Weddings-FBP_0048.jpg
1967 ms
2015Weddings-FBP_0049.jpg
2001 ms
2015Weddings-FBP_0050.jpg
2543 ms
2015Weddings-FBP_0053.jpg
2465 ms
2015Weddings-FBP_0056.jpg
2956 ms
2015Weddings-FBP_0058.jpg
3013 ms
2015Weddings-FBP_0061.jpg
3536 ms
2015Weddings-FBP_0063.jpg
3433 ms
2015Weddings-FBP_0064.jpg
3843 ms
2015Weddings-FBP_0065.jpg
3990 ms
2015Weddings-FBP_0069.jpg
4342 ms
2015Weddings-FBP_0070.jpg
4476 ms
2015Weddings-FBP_0074.jpg
4893 ms
2015Weddings-FBP_0075.jpg
4873 ms
2015Weddings-FBP_0077.jpg
8476 ms
2015Weddings-FBP_0080.jpg
9231 ms
2015Weddings-FBP_0082.jpg
6444 ms
2015Weddings-FBP_0090.jpg
6684 ms
2015Weddings-FBP_0091.jpg
10780 ms
2015Weddings-FBP_0092.jpg
6589 ms
2015Weddings-FBP_0094.jpg
7129 ms
2015Weddings-FBP_0096.jpg
7111 ms
2015Weddings-FBP_0098.jpg
7542 ms
2015Weddings-FBP_0101.jpg
7588 ms
funnybunnyphoto.com accessibility score
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.
funnybunnyphoto.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
funnybunnyphoto.com SEO score
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 Funnybunnyphoto.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 Funnybunnyphoto.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.
funnybunnyphoto.com
Open Graph data is detected on the main page of Funnybunnyphoto. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: