Tools & Wizards About Us
fotogpx.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

fotogpx.com

Guarda tus fotos y visualízalas exactamente en el lugar donde fueron tomadas

Page Load Speed

4 sec in total

First Response

398 ms

Resources Loaded

3.5 sec

Page Rendered

127 ms

fotogpx.com screenshot

About Website

Click here to check amazing Fotogpx content. Otherwise, check out these important facts you probably never knew about fotogpx.com

fotoGPX te propone una forma fácil y rápida de guardar y recordar tus viajes. Sube el track de tu viaje y las fotos y las verás en el mapa en el lugar donde fueron tomadas. Geolocalización de fotos.

Visit fotogpx.com

Key Findings

We analyzed Fotogpx.com page load time and found that the first response time was 398 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

fotogpx.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.47

18/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

fotogpx.com

398 ms

colorbox.css

155 ms

sexylightbox.css

158 ms

tooltipster.css

157 ms

uniform.default.css

157 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 62% of them (58 requests) were addressed to the original Fotogpx.com, 9% (8 requests) were made to Apis.google.com and 3% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fotogpx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (39%)

Content Size

3.9 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fotogpx.com main page is 3.9 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. 60% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 59.8 kB

  • Original 83.9 kB
  • After minification 80.5 kB
  • After compression 24.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 59.8 kB or 71% of the original size.

Image Optimization

-27%

Potential reduce by 772.9 kB

  • Original 2.8 MB
  • After minification 2.1 MB

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. Obviously, Fotogpx needs image optimization as it can save up to 772.9 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 545.9 kB

  • Original 820.0 kB
  • After minification 759.8 kB
  • After compression 274.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 545.9 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 122.7 kB

  • Original 144.7 kB
  • After minification 107.9 kB
  • After compression 21.9 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. Fotogpx.com needs all CSS files to be minified and compressed as it can save up to 122.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (67%)

Requests Now

92

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fotogpx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fotogpx.com

fotogpx.com

398 ms

colorbox.css

colorbox.css

155 ms

sexylightbox.css

sexylightbox.css

158 ms

tooltipster.css

tooltipster.css

157 ms

uniform.default.css

uniform.default.css

157 ms

buscocio.css

buscocio.css

159 ms

jquery.js

jquery.js

381 ms

jquery.autocomplete.pack.js

jquery.autocomplete.pack.js

308 ms

jquery.blockUI.js

jquery.blockUI.js

401 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

309 ms

inview.js

inview.js

308 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

310 ms

sexylightbox.v2.3.jquery.js

sexylightbox.v2.3.jquery.js

536 ms

general.js

general.js

462 ms

jquery.tooltipster.min.js

jquery.tooltipster.min.js

464 ms

jquery.uniform.js

jquery.uniform.js

465 ms

jquery.noty.js

jquery.noty.js

607 ms

bottom.js

bottom.js

546 ms

bottomRight.js

bottomRight.js

612 ms

inline.js

inline.js

615 ms

top.js

top.js

621 ms

topCenter.js

topCenter.js

686 ms

topLeft.js

topLeft.js

702 ms

topRight.js

topRight.js

760 ms

default.js

default.js

764 ms

jquery.simplyscroll.css

jquery.simplyscroll.css

766 ms

jquerytour.css

jquerytour.css

777 ms

exceptions.css

exceptions.css

846 ms

jquery.simplyscroll.min.js

jquery.simplyscroll.min.js

853 ms

jquery-ui-1.8.6.custom.css

jquery-ui-1.8.6.custom.css

912 ms

tooltipster-smoke.css

tooltipster-smoke.css

919 ms

style.css

style.css

922 ms

script.js

script.js

1003 ms

style.responsive.css

style.responsive.css

997 ms

script.responsive.js

script.responsive.js

1007 ms

js_header.php

js_header.php

1081 ms

all.js

all.js

11 ms

addthis_widget.js

addthis_widget.js

14 ms

historial_alexa.php

historial_alexa.php

501 ms

cookietool.css

cookietool.css

556 ms

cookietool.js

cookietool.js

712 ms

mini_logo_factinet.gif

mini_logo_factinet.gif

667 ms

nav.png

nav.png

113 ms

facebook-32x32.png

facebook-32x32.png

113 ms

twitter-32x32.png

twitter-32x32.png

181 ms

googleplus-32x32.png

googleplus-32x32.png

181 ms

spacer.gif

spacer.gif

217 ms

widgets.js

widgets.js

31 ms

183 ms

xd_arbiter.php

xd_arbiter.php

25 ms

xd_arbiter.php

xd_arbiter.php

43 ms

plusone.js

plusone.js

105 ms

cee274f0a7fb859aa81a8d0006efb2dfe5111ecef3.html

cee274f0a7fb859aa81a8d0006efb2dfe5111ecef3.html

166 ms

logo40.gif

logo40.gif

181 ms

counter.js

counter.js

23 ms

t.php

t.php

70 ms

piwik.js

piwik.js

640 ms

300lo.json

300lo.json

43 ms

counter.5524cceca805eb4b9b2b.js

counter.5524cceca805eb4b9b2b.js

36 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

74 ms

border1.png

border1.png

119 ms

border2.png

border2.png

172 ms

loading.gif

loading.gif

172 ms

bgSexy.png

bgSexy.png

179 ms

buttons.png

buttons.png

178 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

45 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

47 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

69 ms

fastbutton

fastbutton

105 ms

shares.json

shares.json

31 ms

TweenMax.min.js

TweenMax.min.js

392 ms

postmessageRelay

postmessageRelay

69 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.es.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.es.html

29 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

38 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

30 ms

like.php

like.php

114 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

43 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

20 ms

rpc:shindig_random.js

rpc:shindig_random.js

44 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

29 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

19 ms

jot

jot

113 ms

52fed58458ef257flSzSmR7BjfoZRPhqw.png

52fed58458ef257flSzSmR7BjfoZRPhqw.png

1169 ms

52fed58544314gPgMfospyOTHNbtF06Ng.png

52fed58544314gPgMfospyOTHNbtF06Ng.png

155 ms

52fed585ce49cd22Rocwbn0Gq6P4C8ok6.png

52fed585ce49cd22Rocwbn0Gq6P4C8ok6.png

155 ms

52fed5864be48fjIEaMWWciOcR5BHyizi.png

52fed5864be48fjIEaMWWciOcR5BHyizi.png

156 ms

52fed5a6e9584v1Tm2k27jdGGylBGLd0L.png

52fed5a6e9584v1Tm2k27jdGGylBGLd0L.png

781 ms

52fed5a782636Ln6J9AZv48GUA981N5nY.png

52fed5a782636Ln6J9AZv48GUA981N5nY.png

162 ms

52fed5a7e5745rtaYuyOuFSgDx8hUTnvU.png

52fed5a7e5745rtaYuyOuFSgDx8hUTnvU.png

307 ms

52fed5a886390sKRFEDf9Cp6hOba1Rd9p.png

52fed5a886390sKRFEDf9Cp6hOba1Rd9p.png

307 ms

52fed5a9080d0vuH2wL0xHJoOlApmpiVc.png

52fed5a9080d0vuH2wL0xHJoOlApmpiVc.png

315 ms

piwik.php

piwik.php

966 ms

print.css

print.css

78 ms

Accessibility Review

fotogpx.com accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fotogpx.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fotogpx.com SEO score

80

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fotogpx.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 Fotogpx.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

fotogpx.com

Open Graph description is not detected on the main page of Fotogpx. 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: