1.7 sec in total
38 ms
1.1 sec
624 ms
Visit furby.es now to see the best up-to-date Furby content for Spain and also check out these interesting facts you probably never knew about furby.es
¿Quieres jugar con tu Furby y Furblings? ¡Encuéntralo todo aquí! ¡Enfrenta a Furby Boom y Furblings entre sí en Furball y completa para desbloquear nuevos huevos Furby Boom!
Visit furby.esWe analyzed Furby.es page load time and found that the first response time was 38 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 30% of websites can load faster.
furby.es performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value17.6 s
0/100
25%
Value6.5 s
39/100
10%
Value260 ms
83/100
30%
Value0.127
82/100
15%
Value9.1 s
33/100
10%
38 ms
42 ms
16 ms
19 ms
18 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Furby.es, 15% (13 requests) were made to Sad.hasbro.com and 9% (8 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (311 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 173.5 kB (8%)
2.1 MB
1.9 MB
In fact, the total size of Furby.es main page is 2.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. 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 61.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. This page needs HTML code to be minified as it can gain 18.9 kB, which is 26% 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 61.1 kB or 85% of the original size.
Potential reduce by 112.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. Furby images are well optimized though.
Number of requests can be reduced by 35 (45%)
78
43
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Furby. 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 10 to 1 for CSS and as a result speed up the page load time.
furby
38 ms
styles.css
42 ms
styles-intl.css
16 ms
super_footer.css
19 ms
language_dropdown.css
18 ms
ebp.css
20 ms
dropdown.css
19 ms
furby.css
25 ms
app-store-buttons.css
25 ms
html5-shiv.js
34 ms
swfobject.js
23 ms
cookie.js
24 ms
ijv0ash.js
81 ms
jquery.min.js
30 ms
jquery.touchSwipe.js
54 ms
metrics.helper.min.js
26 ms
s_code.js
33 ms
jquery.easing.1.3.js
30 ms
hmac-sha256.js
45 ms
hapi.js
50 ms
common_tracking.js
49 ms
leave_hasbro.js
50 ms
respond.min.js
63 ms
toy-finder.js
49 ms
custom.js
51 ms
BrightcoveExperiences_all.js
54 ms
BCSmartPlayer.js
50 ms
hero_carousel.js
53 ms
omniture.js
53 ms
dropdown_button_clicks.js
53 ms
search-input.js
54 ms
carousel.js
56 ms
module_slider.js
57 ms
aunz_price_swap.js
57 ms
jquery.fancybox.css
58 ms
jquery.fancybox.pack.js
57 ms
tracking_send.js
80 ms
www.hasbro.com
131 ms
logo_hasbro.png
61 ms
6c95b2ebe11d7267d6a462b04c79c163.png
65 ms
36b87a141a5bd477009d0a9383a2e184.png
158 ms
b357b0f78487e41764e6fcb41d8bdb07.png
89 ms
2b52664af0116fdef011213b9e4f1591.png
158 ms
a23f247988e5dc19686f9dd358ad195c.png
89 ms
128c270c1f46c8a7010964e35be0509b.png
88 ms
609f38b2d7a1923369a330db565b8ad1.png
90 ms
b99c219ed4367bf64ce3ffac66551722.png
163 ms
30f0feb17fad51b6703c1b02fdddd43c.png
169 ms
0700c33edda505cfea13f94677c3d092.png
166 ms
b88510bf4b337d148835350819bf161f.png
167 ms
950b2ca4f2e6f25c06f137196e6c69b1.png
163 ms
0bd68c2efbab181a9fe0019f55ceba53.png
173 ms
logo_furby
57 ms
0E0B8A6F50569047F51B3513A4DBE392.jpg
82 ms
B608DC7B50569047F59AF0519AC7213E.jpg
84 ms
B60D232050569047F5ACE481B2ADAAA7.jpg
57 ms
B60BE26F50569047F5EA0F303CE8EA7C.jpg
57 ms
B60A51F850569047F544E51530CB1D8C.jpg
82 ms
B60F1B6B50569047F552CFCF184FB07E.jpg
155 ms
1D3F429750569047F555830DB3C0AFB1.jpg
159 ms
1D3FEA2250569047F50DAA26190F4EAF.jpg
157 ms
0E151B8C50569047F5AF32915A84432A.jpg
168 ms
0E3B734950569047F575924BE4BFDC2E.jpg
159 ms
1D4086A150569047F50916D98BB7ECB2.jpg
166 ms
0E415C4B50569047F5E6AF8BDBC2987A.jpg
170 ms
6691051650569047F570D4A009E90419.png
171 ms
6687120150569047F5D4592742B202FD.png
160 ms
dohvinci.jpg
159 ms
furreal.jpg
161 ms
footerlogo.png
161 ms
sprite_common.png
117 ms
arrow_down.png
116 ms
icon_worldwide.png
118 ms
bgbrand_furby.png
121 ms
charsprite_furby.png
291 ms
bg_navarrows.png
119 ms
sprite_apps.png
117 ms
xdTJgGPceUw_jFpWRob1HPV55RdyT8Hr5R78KovHzbCffHAsgsMWeMJ6Mk6f5Mt.woff
82 ms
E0hxi_3hn3_v25wAnBK7VXzXJf3GrqgFJAqINWBglwJffHpsgsMWeMJ6Mk6f5gM.woff
256 ms
GqUjmkyqKQcm0icQyT-IsnhRG4KRG7qtlyh3R_PVrjIffHcsgsMWeMJ6Mk6f5gI.woff
280 ms
UIYMwGx0LuWrDD3emvxaFPrUhyg43RStBk7HR2IeLLCffHPsgsMWeMJ6Mk6f5Mb.woff
305 ms
9MY4rQst_yoewQrO5EaaLiOcO1gbP2x0Qd522fn64tvffH-sgsMWeMJ6Mk6f5Mj.woff
310 ms
gPj0djVu1JBjQJslz39e6n4fQZxyz6--jy1-K-qqan6ff4kQgsMWeMJ6Mk6f5MS.woff
311 ms
6687120150569047F5D4592742B202FD.png
181 ms
6691051650569047F570D4A009E90419.png
195 ms
6687120150569047F5D4592742B202FD.png
25 ms
6691051650569047F570D4A009E90419.png
59 ms
p.gif
115 ms
s47409445138182
83 ms
furby.es accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
furby.es 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
furby.es SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Furby.es 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 Furby.es 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.
furby.es
Open Graph description is not detected on the main page of Furby. 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: