6.8 sec in total
1.3 sec
4.9 sec
714 ms
Welcome to fernandortega.com homepage info - get ready to check Fernando Rtega best content right away, or after learning these important things about fernandortega.com
Fernando Ortega | Vagamundos | Photographer | Creative Photography | Travel | Fashion Photography | Moon Art Space Director
Visit fernandortega.comWe analyzed Fernandortega.com page load time and found that the first response time was 1.3 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fernandortega.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value14.2 s
0/100
25%
Value11.4 s
5/100
10%
Value890 ms
32/100
30%
Value0.029
100/100
15%
Value14.1 s
10/100
10%
1281 ms
135 ms
259 ms
23 ms
113 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 91% of them (49 requests) were addressed to the original Fernandortega.com, 4% (2 requests) were made to Google.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Fernandortega.com.
Page size can be reduced by 494.0 kB (18%)
2.8 MB
2.3 MB
In fact, the total size of Fernandortega.com main page is 2.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. 50% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 27.2 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 27.2 kB or 78% of the original size.
Potential reduce by 175.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. Fernando Rtega images are well optimized though.
Potential reduce by 185.1 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 185.1 kB or 69% of the original size.
Potential reduce by 106.3 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. Fernandortega.com needs all CSS files to be minified and compressed as it can save up to 106.3 kB or 84% of the original size.
Number of requests can be reduced by 21 (40%)
52
31
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fernando Rtega. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.fernandortega.com
1281 ms
prettyPhoto.css
135 ms
nivo-slider.css
259 ms
css
23 ms
fonts
113 ms
style.css
280 ms
white-skin.css
262 ms
cssLoader.php
636 ms
responsive.css
276 ms
diggdigg-style.css
284 ms
easy-author-image.css
375 ms
jquery.js
518 ms
jquery-migrate.min.js
408 ms
main.js
545 ms
jquery.nivo.slider.pack.js
413 ms
wp-embed.min.js
493 ms
comment-reply.min.js
537 ms
fonts
137 ms
wp-emoji-release.min.js
131 ms
analytics.js
30 ms
noise_w.png
192 ms
1456841794Sin%20t%C3%ADtulo3.gif
249 ms
timthumb.php
947 ms
timthumb.php
853 ms
timthumb.php
942 ms
timthumb.php
993 ms
timthumb.php
1068 ms
timthumb.php
1001 ms
timthumb.php
1461 ms
FOV2617-980x390.jpg
1075 ms
FOV1385-475x230.jpg
1082 ms
FOV1894-2-475x230.jpg
1120 ms
web3-475x230.jpg
1124 ms
FOV6873-475x230.jpg
1329 ms
Cartel-Exposici%C3%B3n-Auschwitz-Birkenau-page0001-475x230.jpg
1207 ms
cartel_calendario_barber_portada_peq-475x230.gif
1213 ms
IMG-475x230.jpg
1248 ms
FOV9969-475x230.jpg
1247 ms
FOV8634-1-475x230.jpg
1339 ms
FOV8171-1-475x230.jpg
1347 ms
twitter.png
1371 ms
facebook.png
1373 ms
instagram.png
1460 ms
linkedin.png
1472 ms
google-plus2.png
1479 ms
flickr.png
1493 ms
youtube.png
1499 ms
ajax-loader-w.gif
1568 ms
trans.png
1580 ms
pattern3.png
1593 ms
collect
13 ms
preview_arrows.png
129 ms
page_nav_active_black.png
135 ms
page_nav.png
126 ms
fernandortega.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
fernandortega.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
fernandortega.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fernandortega.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Fernandortega.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.
fernandortega.com
Open Graph data is detected on the main page of Fernando Rtega. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: