Tools & Wizards About Us
pareja.org.es screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    75% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

pareja.org.es

Buscar pareja en Internet

Page Load Speed

3.4 sec in total

First Response

387 ms

Resources Loaded

2.8 sec

Page Rendered

293 ms

pareja.org.es screenshot

About Website

Click here to check amazing Pareja content. Otherwise, check out these important facts you probably never knew about pareja.org.es

La forma más sencilla de encontrar pareja.

Visit pareja.org.es

Key Findings

We analyzed Pareja.org.es page load time and found that the first response time was 387 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

pareja.org.es performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

81/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

pareja.org.es

387 ms

style.css

53 ms

jquery-1.6.1.min.js

76 ms

jquery.cycle.js

57 ms

slider.js

56 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 33% of them (27 requests) were addressed to the original Pareja.org.es, 12% (10 requests) were made to Static.xx.fbcdn.net and 10% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (623 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 389.7 kB (52%)

Content Size

745.3 kB

After Optimization

355.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pareja.org.es main page is 745.3 kB. 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. Javascripts take 396.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 84.6 kB

  • Original 108.2 kB
  • After minification 106.0 kB
  • After compression 23.6 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 84.6 kB or 78% of the original size.

Image Optimization

-11%

Potential reduce by 20.9 kB

  • Original 199.0 kB
  • After minification 178.1 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. Obviously, Pareja needs image optimization as it can save up to 20.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 250.2 kB

  • Original 396.4 kB
  • After minification 390.9 kB
  • After compression 146.2 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 250.2 kB or 63% of the original size.

CSS Optimization

-81%

Potential reduce by 34.0 kB

  • Original 41.8 kB
  • After minification 33.1 kB
  • After compression 7.8 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. Pareja.org.es needs all CSS files to be minified and compressed as it can save up to 34.0 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (63%)

Requests Now

78

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pareja.org.es

pareja.org.es

387 ms

style.css

style.css

53 ms

jquery-1.6.1.min.js

jquery-1.6.1.min.js

76 ms

jquery.cycle.js

jquery.cycle.js

57 ms

slider.js

slider.js

56 ms

superfish.js

superfish.js

56 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

76 ms

jquery.rating.pack.js

jquery.rating.pack.js

87 ms

jquery.js

jquery.js

157 ms

jquery-migrate.min.js

jquery-migrate.min.js

85 ms

default.css

default.css

354 ms

plusone.js

plusone.js

53 ms

adsbygoogle.js

adsbygoogle.js

22 ms

all.js

all.js

271 ms

widgets.js

widgets.js

10 ms

pinit.js

pinit.js

60 ms

custom.js

custom.js

55 ms

reset.css

reset.css

51 ms

superfish.css

superfish.css

63 ms

slider-style.css

slider-style.css

64 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

75 ms

jquery.rating.css

jquery.rating.css

77 ms

ga.js

ga.js

18 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

28 ms

__utm.gif

__utm.gif

12 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

10 ms

optimum-red.jpg

optimum-red.jpg

90 ms

topbg.jpg

topbg.jpg

89 ms

fondo.jpg

fondo.jpg

88 ms

logo.png

logo.png

174 ms

body-bg.gif

body-bg.gif

89 ms

cat_bg.png

cat_bg.png

88 ms

ca-pub-1557632363501269.js

ca-pub-1557632363501269.js

74 ms

zrt_lookup.html

zrt_lookup.html

152 ms

show_ads_impl.js

show_ads_impl.js

92 ms

auth_icon.png

auth_icon.png

148 ms

255 ms

xd_arbiter.php

xd_arbiter.php

250 ms

xd_arbiter.php

xd_arbiter.php

459 ms

ads

ads

246 ms

osd.js

osd.js

15 ms

ads

ads

295 ms

ads

ads

172 ms

ads

ads

180 ms

ads

ads

279 ms

foot_top.jpg

foot_top.jpg

89 ms

foot_bottom.jpg

foot_bottom.jpg

34 ms

__utm.gif

__utm.gif

30 ms

__utm.gif

__utm.gif

57 ms

pinit_main.js

pinit_main.js

124 ms

abg.js

abg.js

47 ms

m_js_controller.js

m_js_controller.js

34 ms

favicon

favicon

84 ms

s

s

70 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

83 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

68 ms

x_button_blue2.png

x_button_blue2.png

68 ms

13221747130921273961

13221747130921273961

54 ms

favicon

favicon

28 ms

fan.php

fan.php

239 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

5 ms

ui

ui

73 ms

kyEKgjk51ZE.css

kyEKgjk51ZE.css

286 ms

xgj7bXhJNEH.css

xgj7bXhJNEH.css

354 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

493 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

623 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

491 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

491 ms

558569_290279691066844_1867914919_n.jpg

558569_290279691066844_1867914919_n.jpg

339 ms

577588_290223534405793_793086616_n.jpg

577588_290223534405793_793086616_n.jpg

406 ms

12733989_1082139028496233_8012605593684582647_n.jpg

12733989_1082139028496233_8012605593684582647_n.jpg

476 ms

557648_2182675022122_1392695696_n.jpg

557648_2182675022122_1392695696_n.jpg

538 ms

12346566_489031337943904_3973235728432480689_n.jpg

12346566_489031337943904_3973235728432480689_n.jpg

540 ms

12814624_223605674654188_6368718851409052035_n.jpg

12814624_223605674654188_6368718851409052035_n.jpg

540 ms

12717609_204523649906614_2983045933518036558_n.jpg

12717609_204523649906614_2983045933518036558_n.jpg

543 ms

533778_1380874058812536_1561376896_n.jpg

533778_1380874058812536_1561376896_n.jpg

569 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

83 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

82 ms

activeview

activeview

14 ms

activeview

activeview

18 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

69 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

71 ms

Accessibility Review

pareja.org.es accessibility score

85

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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

Best Practices

pareja.org.es best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pareja.org.es SEO score

71

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pareja.org.es 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 Pareja.org.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.

Social Sharing Optimization

pareja.org.es

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