Tools & Wizards About Us
fotogpx.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

fotogpx.com

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

Page Load Speed

3.8 sec in total

First Response

345 ms

Resources Loaded

3.3 sec

Page Rendered

88 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 345 ms and then it took 3.4 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

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.471

18/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

fotogpx.com

345 ms

fotogpx.com

519 ms

colorbox.css

114 ms

sexylightbox.css

225 ms

tooltipster.css

319 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 74% of them (59 requests) were addressed to the original Fotogpx.com, 5% (4 requests) were made to Platform.twitter.com and 4% (3 requests) were made to Factinet.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Fotogpx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (33%)

Content Size

3.4 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fotogpx.com main page is 3.4 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.8 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 28.5 kB

  • Original 36.9 kB
  • After minification 32.8 kB
  • After compression 8.4 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 4.0 kB, which is 11% 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 28.5 kB or 77% of the original size.

Image Optimization

-25%

Potential reduce by 713.8 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 713.8 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 273.8 kB

  • Original 396.9 kB
  • After minification 334.3 kB
  • After compression 123.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 273.8 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 124.5 kB

  • Original 147.0 kB
  • After minification 110.2 kB
  • After compression 22.5 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 124.5 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

76

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 76 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 33 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fotogpx.com

fotogpx.com

345 ms

fotogpx.com

fotogpx.com

519 ms

colorbox.css

colorbox.css

114 ms

sexylightbox.css

sexylightbox.css

225 ms

tooltipster.css

tooltipster.css

319 ms

uniform.default.css

uniform.default.css

320 ms

buscocio.css

buscocio.css

449 ms

jquery.js

jquery.js

562 ms

jquery.autocomplete.pack.js

jquery.autocomplete.pack.js

336 ms

jquery.blockUI.js

jquery.blockUI.js

476 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

424 ms

inview.js

inview.js

425 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

450 ms

sexylightbox.v2.3.jquery.js

sexylightbox.v2.3.jquery.js

635 ms

general.js

general.js

531 ms

jquery.tooltipster.min.js

jquery.tooltipster.min.js

561 ms

jquery.uniform.js

jquery.uniform.js

574 ms

jquery.noty.js

jquery.noty.js

595 ms

bottom.js

bottom.js

638 ms

bottomRight.js

bottomRight.js

675 ms

inline.js

inline.js

674 ms

top.js

top.js

673 ms

topCenter.js

topCenter.js

714 ms

topLeft.js

topLeft.js

741 ms

topRight.js

topRight.js

744 ms

default.js

default.js

785 ms

jquery.simplyscroll.css

jquery.simplyscroll.css

786 ms

jquerytour.css

jquerytour.css

786 ms

exceptions.css

exceptions.css

833 ms

jquery.simplyscroll.min.js

jquery.simplyscroll.min.js

846 ms

jquery-ui-1.8.6.custom.css

jquery-ui-1.8.6.custom.css

955 ms

tooltipster-smoke.css

tooltipster-smoke.css

897 ms

style.css

style.css

1008 ms

script.js

script.js

898 ms

style.responsive.css

style.responsive.css

952 ms

script.responsive.js

script.responsive.js

952 ms

js_header.php

js_header.php

1026 ms

all.js

all.js

23 ms

addthis_widget.js

addthis_widget.js

31 ms

js

js

66 ms

jquery.ihavecookies.min.js

jquery.ihavecookies.min.js

690 ms

css

css

45 ms

jquery.ihavecookies.css

jquery.ihavecookies.css

689 ms

mini_logo_factinet.gif

mini_logo_factinet.gif

141 ms

nav.png

nav.png

142 ms

facebook-32x32.png

facebook-32x32.png

142 ms

twitter-32x32.png

twitter-32x32.png

141 ms

googleplus-32x32.png

googleplus-32x32.png

141 ms

spacer.gif

spacer.gif

127 ms

widgets.js

widgets.js

46 ms

all.js

all.js

9 ms

cee274f0a7fb859aa81a8d0006efb2dfe5111ecef3.html

cee274f0a7fb859aa81a8d0006efb2dfe5111ecef3.html

121 ms

counter.js

counter.js

71 ms

t.php

t.php

122 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

24 ms

border1.png

border1.png

122 ms

border2.png

border2.png

124 ms

loading.gif

loading.gif

123 ms

bgSexy.png

bgSexy.png

122 ms

buttons.png

buttons.png

119 ms

like.php

like.php

480 ms

TweenMax.min.js

TweenMax.min.js

212 ms

settings

settings

72 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

2 ms

embeds

embeds

22 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.es.html

tweet_button.2f70fb173b9000da126c79afe2098f02.es.html

12 ms

52fed58458ef257flSzSmR7BjfoZRPhqw.png

52fed58458ef257flSzSmR7BjfoZRPhqw.png

898 ms

52fed58544314gPgMfospyOTHNbtF06Ng.png

52fed58544314gPgMfospyOTHNbtF06Ng.png

121 ms

52fed585ce49cd22Rocwbn0Gq6P4C8ok6.png

52fed585ce49cd22Rocwbn0Gq6P4C8ok6.png

113 ms

52fed5864be48fjIEaMWWciOcR5BHyizi.png

52fed5864be48fjIEaMWWciOcR5BHyizi.png

114 ms

52fed5a6e9584v1Tm2k27jdGGylBGLd0L.png

52fed5a6e9584v1Tm2k27jdGGylBGLd0L.png

530 ms

52fed5a782636Ln6J9AZv48GUA981N5nY.png

52fed5a782636Ln6J9AZv48GUA981N5nY.png

108 ms

52fed5a7e5745rtaYuyOuFSgDx8hUTnvU.png

52fed5a7e5745rtaYuyOuFSgDx8hUTnvU.png

213 ms

52fed5a886390sKRFEDf9Cp6hOba1Rd9p.png

52fed5a886390sKRFEDf9Cp6hOba1Rd9p.png

226 ms

52fed5a9080d0vuH2wL0xHJoOlApmpiVc.png

52fed5a9080d0vuH2wL0xHJoOlApmpiVc.png

225 ms

khYakkszxHp.js

khYakkszxHp.js

88 ms

FEppCFCt76d.png

FEppCFCt76d.png

10 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58a-xw.ttf

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58a-xw.ttf

19 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf

26 ms

print.css

print.css

113 ms

Accessibility Review

fotogpx.com accessibility score

75

Accessibility Issues

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

High

Links do not have a discernible name

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

88

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

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: