Tools & Wizards About Us
foroloco.org screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

foroloco.org

Foro Loco - Foros

Page Load Speed

4.3 sec in total

First Response

737 ms

Resources Loaded

3.3 sec

Page Rendered

213 ms

foroloco.org screenshot

About Website

Click here to check amazing Foro Loco content for Russia. Otherwise, check out these important facts you probably never knew about foroloco.org

Cajón de Sastre, La Casa Real, La Crispación, Foro Loko, ¿Acabas de llegar a Foroloco?, Chat

Visit foroloco.org

Key Findings

We analyzed Foroloco.org page load time and found that the first response time was 737 ms and then it took 3.5 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

foroloco.org performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value14.5 s

8/100

10%

Network Requests Diagram

foroloco.org

737 ms

adsbygoogle.js

147 ms

stylesheet.css

216 ms

stylesheet.css

220 ms

smiley.css

218 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 54% of them (46 requests) were addressed to the original Foroloco.org, 9% (8 requests) were made to Googleads.g.doubleclick.net and 8% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Foroloco.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 905.1 kB (49%)

Content Size

1.9 MB

After Optimization

946.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foroloco.org main page is 1.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. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 67.0 kB

  • Original 78.0 kB
  • After minification 74.3 kB
  • After compression 11.0 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 67.0 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 1.0 kB

  • Original 296.0 kB
  • After minification 295.0 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. Foro Loco images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 677.6 kB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 603.6 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 677.6 kB or 53% of the original size.

CSS Optimization

-81%

Potential reduce by 159.5 kB

  • Original 196.6 kB
  • After minification 154.3 kB
  • After compression 37.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. Foroloco.org needs all CSS files to be minified and compressed as it can save up to 159.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (72%)

Requests Now

82

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

foroloco.org

foroloco.org

737 ms

adsbygoogle.js

adsbygoogle.js

147 ms

stylesheet.css

stylesheet.css

216 ms

stylesheet.css

stylesheet.css

220 ms

smiley.css

smiley.css

218 ms

lastpostavatar.css

lastpostavatar.css

221 ms

rules.css

rules.css

221 ms

quotethumbnails.css

quotethumbnails.css

282 ms

jwplayer.js

jwplayer.js

570 ms

show_ads.js

show_ads.js

73 ms

jquery.min.js

jquery.min.js

580 ms

core.js

core.js

488 ms

forum_fn.js

forum_fn.js

390 ms

ajax.js

ajax.js

298 ms

strip.min.js

strip.min.js

575 ms

map.js

map.js

131 ms

show_ads_impl.js

show_ads_impl.js

293 ms

common.css

common.css

464 ms

links.css

links.css

457 ms

content.css

content.css

549 ms

buttons.css

buttons.css

554 ms

cp.css

cp.css

643 ms

forms.css

forms.css

645 ms

colours.css

colours.css

744 ms

imageset.css

imageset.css

652 ms

iframe.css

iframe.css

738 ms

font-awesome.min.css

font-awesome.min.css

838 ms

common.css

common.css

831 ms

content.css

content.css

929 ms

cp.css

cp.css

839 ms

forms.css

forms.css

929 ms

strip.css

strip.css

934 ms

iframe.css

iframe.css

1020 ms

cajon_de_sastre.jpg

cajon_de_sastre.jpg

328 ms

dashboard.jpg

dashboard.jpg

302 ms

no_avatar.gif

no_avatar.gif

212 ms

casa_real.jpg

casa_real.jpg

422 ms

crispacion.png

crispacion.png

423 ms

foroloko.jpg

foroloko.jpg

330 ms

presentate.png

presentate.png

235 ms

chat.png

chat.png

331 ms

forum_read.gif

forum_read.gif

191 ms

icon_topic_latest.gif

icon_topic_latest.gif

192 ms

forum_read_locked.gif

forum_read_locked.gif

192 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

387 ms

zrt_lookup.html

zrt_lookup.html

71 ms

ads

ads

512 ms

ads

ads

480 ms

222 ms

counter.js

counter.js

37 ms

icon_rules.gif

icon_rules.gif

285 ms

alert_close.png

alert_close.png

309 ms

t.php

t.php

104 ms

72 ms

close.svg

close.svg

228 ms

balloon.min.css

balloon.min.css

16 ms

neosat.jpg

neosat.jpg

28 ms

star-blue.png

star-blue.png

27 ms

200 ms

tag.min.js

tag.min.js

18 ms

195 ms

responsive.css

responsive.css

98 ms

lt.min.js

lt.min.js

30 ms

responsive.css

responsive.css

302 ms

load_preloaded_resource.js

load_preloaded_resource.js

164 ms

icon.png

icon.png

11 ms

abg_lite.js

abg_lite.js

160 ms

s

s

29 ms

window_focus.js

window_focus.js

168 ms

qs_click_protection.js

qs_click_protection.js

169 ms

ufs_web_display.js

ufs_web_display.js

53 ms

60efddb729a951d3495fe79f6eb41a86.js

60efddb729a951d3495fe79f6eb41a86.js

274 ms

reactive_library.js

reactive_library.js

269 ms

ads

ads

692 ms

ads

ads

385 ms

ads

ads

390 ms

css

css

50 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

8 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

33 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

48 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

51 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

54 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

54 ms

activeview

activeview

115 ms

wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js

wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js

30 ms

Accessibility Review

foroloco.org accessibility score

72

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

High

Image elements do not have [alt] attributes

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

High

Some elements have a [tabindex] value greater than 0

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

foroloco.org 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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

foroloco.org SEO score

83

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

Content Best Practices

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Foroloco.org 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 Foroloco.org 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

foroloco.org

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