3 sec in total
1.2 sec
1.8 sec
58 ms
Visit fernandoorellana.com now to see the best up-to-date Fernando Orellana content and also check out these interesting facts you probably never knew about fernandoorellana.com
Fernando Orellana works in range of media including paint, pixels, robotics and Play-Doh. This site documents a variety of his projects going back to 1998.
Visit fernandoorellana.comWe analyzed Fernandoorellana.com page load time and found that the first response time was 1.2 sec and then it took 1.8 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.
fernandoorellana.com performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value3.8 s
55/100
25%
Value10.8 s
6/100
10%
Value280 ms
80/100
30%
Value0
100/100
15%
Value12.0 s
16/100
10%
1226 ms
51 ms
52 ms
80 ms
72 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 73% of them (61 requests) were addressed to the original Fernandoorellana.com, 22% (18 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fernandoorellana.com.
Page size can be reduced by 273.7 kB (10%)
2.6 MB
2.3 MB
In fact, the total size of Fernandoorellana.com main page is 2.6 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.4 MB which makes up the majority of the site volume.
Potential reduce by 31.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 31.1 kB or 81% of the original size.
Potential reduce by 117.5 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. Fernando Orellana images are well optimized though.
Potential reduce by 109.0 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 109.0 kB or 64% of the original size.
Potential reduce by 16.1 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. Fernandoorellana.com needs all CSS files to be minified and compressed as it can save up to 16.1 kB or 84% of the original size.
Number of requests can be reduced by 20 (25%)
81
61
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fernando Orellana. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
fernandoorellana.com
1226 ms
global.css
51 ms
flickity.css
52 ms
libs.js
80 ms
flickity.pkgd.min.js
72 ms
global.js
120 ms
widgets.js
6 ms
ga.js
38 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
63 ms
thumb_corpo-400x400.jpg
38 ms
IMG_7437-400x400.jpg
58 ms
4_Right_3_4_view_B-400x400.jpg
60 ms
Leftovers_30inx40in-400x400.jpg
58 ms
18_Fernando_Orellana_LaManchaGuernica-400x400.png
109 ms
IMG_0115-1-400x400.jpg
84 ms
IMG_0151-400x400.jpg
78 ms
IMG_0663-400x400.jpg
94 ms
IMG_6533-400x400.jpg
91 ms
middle_Shot-400x400.jpg
94 ms
thumb_me-400x400.jpg
110 ms
Spring_Break_4-400x400.jpg
146 ms
thumb-400x400.jpg
166 ms
thumb_congress-400x400.jpg
116 ms
secondthumb-400x400.jpg
132 ms
thumb-1-400x400.jpg
157 ms
Thumb_governors_THEKING-400x400.jpg
141 ms
thumb_HSL-400x400.jpg
166 ms
confluence_06-2015_0127-400x400.jpg
159 ms
Thumb-400x400.jpg
192 ms
Her_Recipies_3_4-400x400.jpg
174 ms
Population_2012_web-400x400.jpg
204 ms
thumb_2-400x400.jpg
227 ms
face_man_web-400x400.jpg
224 ms
daydreaming_web-400x400.jpg
209 ms
elevator_2_web1-400x400.jpg
198 ms
4-400x400.jpg
232 ms
dm_artbots_2007_web-400x400.jpg
219 ms
close_up_a2-400x400.jpg
227 ms
extruder_detail_web-400x400.jpg
302 ms
broadcasting-400x400.jpg
288 ms
medium-400x400.jpg
288 ms
whale_ride_thumb-400x400.jpg
303 ms
abstract_close_up_sm-400x400.jpg
304 ms
close_up_b-400x400.jpg
289 ms
garaje.woff
303 ms
__utm.gif
16 ms
settings
75 ms
medium_shot_b-400x400.jpg
268 ms
distance5-400x400.jpg
250 ms
medium1-400x400.jpg
247 ms
left-400x400.jpg
259 ms
framed_web-400x400.jpg
241 ms
detail_thumb-400x400.jpg
233 ms
PHONEY_DETAIL-400x400.jpg
228 ms
beta_god_web-400x400.jpg
232 ms
youwant______-400x385.jpg
247 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
2 ms
god_mechanism_web-400x400.jpg
232 ms
All_of_Us_web-400x400.jpg
247 ms
polyfluid
125 ms
misha_thumb-400x400.jpg
242 ms
question_145-400x400.jpg
224 ms
Close_Bot1_thumb-400x400.jpg
215 ms
red_truck_web-400x400.jpg
216 ms
hive_close_up-400x400.jpg
221 ms
chorizo_thumb-400x400.jpg
225 ms
final_machine_web-400x400.jpg
210 ms
tiger_thumb_2.jpg
202 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
5 ms
runtime-b1c52fd0a13ead5fcf6b.js
18 ms
modules-96ebc7ac3ad66d681a3d.js
21 ms
main-babd9234dc048fb47339.js
19 ms
_app-a9c9f1a99e4414675fb1.js
20 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
20 ms
_buildManifest.js
20 ms
_ssgManifest.js
19 ms
8526.0c32a8f0cfc5749221a3.js
11 ms
1755.07a49c40b12af4f75780.js
11 ms
8283.f3e5048cca7cef5eed7f.js
10 ms
3077.44bfeb00af01bc4020f6.js
11 ms
1362.42d432e02f7980bca032.js
9 ms
4956.c4e51ef593974b9db0bb.js
24 ms
5893.d500bd2a89ded806aa73.js
9 ms
fernandoorellana.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.
fernandoorellana.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
fernandoorellana.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fernandoorellana.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 Fernandoorellana.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.
fernandoorellana.com
Open Graph description is not detected on the main page of Fernando Orellana. 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: