Tools & Wizards About Us
foro-adelgazar.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

foro-adelgazar.com

域名到期-域名续费提醒

Page Load Speed

3.7 sec in total

First Response

533 ms

Resources Loaded

2.8 sec

Page Rendered

354 ms

foro-adelgazar.com screenshot

About Website

Visit foro-adelgazar.com now to see the best up-to-date Foro Adelgazar content for Spain and also check out these interesting facts you probably never knew about foro-adelgazar.com

域名是企业重要的资产,您所访问的域名已经过期,请尽快联络注册商续费

Visit foro-adelgazar.com

Key Findings

We analyzed Foro-adelgazar.com page load time and found that the first response time was 533 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

foro-adelgazar.com performance score

0

Network Requests Diagram

foro-adelgazar.com

533 ms

yuiloader-dom-event.js

405 ms

connection-min.js

303 ms

vbulletin-core.js

402 ms

css.php

542 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 71% of them (65 requests) were addressed to the original Foro-adelgazar.com, 11% (10 requests) were made to Static.xx.fbcdn.net and 5% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (688 ms) belongs to the original domain Foro-adelgazar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 327.7 kB (72%)

Content Size

457.9 kB

After Optimization

130.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foro-adelgazar.com main page is 457.9 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. 45% of websites need less resources to load. Javascripts take 190.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 53.6 kB

  • Original 65.0 kB
  • After minification 58.3 kB
  • After compression 11.3 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 53.6 kB or 83% of the original size.

Image Optimization

-50%

Potential reduce by 22.9 kB

  • Original 45.8 kB
  • After minification 23.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. Obviously, Foro Adelgazar needs image optimization as it can save up to 22.9 kB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 119.1 kB

  • Original 190.8 kB
  • After minification 184.9 kB
  • After compression 71.7 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 119.1 kB or 62% of the original size.

CSS Optimization

-85%

Potential reduce by 132.2 kB

  • Original 156.4 kB
  • After minification 121.4 kB
  • After compression 24.2 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. Foro-adelgazar.com needs all CSS files to be minified and compressed as it can save up to 132.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (71%)

Requests Now

90

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

foro-adelgazar.com

foro-adelgazar.com

533 ms

yuiloader-dom-event.js

yuiloader-dom-event.js

405 ms

connection-min.js

connection-min.js

303 ms

vbulletin-core.js

vbulletin-core.js

402 ms

css.php

css.php

542 ms

appbanner.css

appbanner.css

308 ms

appbanner.js

appbanner.js

308 ms

ads.js

ads.js

401 ms

vbulletin_read_marker.js

vbulletin_read_marker.js

424 ms

css.php

css.php

538 ms

css.php

css.php

613 ms

vbulletin-sidebar.js

vbulletin-sidebar.js

499 ms

css.php

css.php

649 ms

css.php

css.php

601 ms

vbulletin_md5.js

vbulletin_md5.js

596 ms

show_ads.js

show_ads.js

7 ms

urchin.js

urchin.js

23 ms

pageBG.gif

pageBG.gif

99 ms

animation-min.js

animation-min.js

101 ms

loginButton.gif

loginButton.gif

139 ms

logo.gif

logo.gif

141 ms

searchButton.gif

searchButton.gif

150 ms

navbit-home.png

navbit-home.png

139 ms

collapse_tcat.png

collapse_tcat.png

149 ms

forum_old-48.png

forum_old-48.png

141 ms

icon8.png

icon8.png

205 ms

lastpost-right.png

lastpost-right.png

203 ms

icon1.png

icon1.png

204 ms

icon3.png

icon3.png

203 ms

subforum_old-48.png

subforum_old-48.png

206 ms

icon5.png

icon5.png

205 ms

users_online.png

users_online.png

299 ms

forum_stats.png

forum_stats.png

302 ms

birthday.png

birthday.png

300 ms

tab-collapsed.png

tab-collapsed.png

301 ms

collapse_40b.png

collapse_40b.png

304 ms

widget-comment.png

widget-comment.png

303 ms

jk5.gif

jk5.gif

469 ms

unknown.gif

unknown.gif

398 ms

clauuc.gif

clauuc.gif

483 ms

footerLogo.gif

footerLogo.gif

398 ms

topBarBG.gif

topBarBG.gif

416 ms

topBarLeft.gif

topBarLeft.gif

403 ms

topBarRight.gif

topBarRight.gif

493 ms

regSplit.gif

regSplit.gif

485 ms

headerBG.gif

headerBG.gif

493 ms

navBG.gif

navBG.gif

501 ms

navEnd.gif

navEnd.gif

554 ms

arrow.png

arrow.png

568 ms

contentBG.gif

contentBG.gif

580 ms

bcBG.gif

bcBG.gif

581 ms

bcLeft.gif

bcLeft.gif

593 ms

bcRight.gif

bcRight.gif

602 ms

ca-pub-1041767568299291.js

ca-pub-1041767568299291.js

52 ms

zrt_lookup.html

zrt_lookup.html

58 ms

show_ads_impl.js

show_ads_impl.js

65 ms

tcatBG.gif

tcatBG.gif

610 ms

tcatLeft.gif

tcatLeft.gif

625 ms

__utm.gif

__utm.gif

13 ms

ads

ads

194 ms

tcatRight.gif

tcatRight.gif

556 ms

theadBG.gif

theadBG.gif

554 ms

rss_40b.png

rss_40b.png

571 ms

bottomBarBG.gif

bottomBarBG.gif

571 ms

bottomBarLeft.gif

bottomBarLeft.gif

617 ms

osd.js

osd.js

22 ms

bottomBarRight.gif

bottomBarRight.gif

629 ms

likebox.php

likebox.php

248 ms

ads

ads

165 ms

ads

ads

210 ms

gradient-greytowhite.png

gradient-greytowhite.png

590 ms

top-highlight.png

top-highlight.png

639 ms

gradient-black-down.png

gradient-black-down.png

609 ms

bottom-shadow.png

bottom-shadow.png

616 ms

footerNav.gif

footerNav.gif

688 ms

footerBG.gif

footerBG.gif

685 ms

jTuqQ-OPDr6.css

jTuqQ-OPDr6.css

280 ms

n370yiaI2G6.css

n370yiaI2G6.css

347 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

484 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

613 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

482 ms

TTCre3391I0.js

TTCre3391I0.js

510 ms

abg.js

abg.js

20 ms

399548_10149999285987789_1102888142_n.png

399548_10149999285987789_1102888142_n.png

280 ms

12373422_10205612772304022_5881027570987805165_n.jpg

12373422_10205612772304022_5881027570987805165_n.jpg

352 ms

10580271_962993750433459_3209043456222387193_n.jpg

10580271_962993750433459_3209043456222387193_n.jpg

420 ms

12049627_10156084287820065_2425763806597329437_n.jpg

12049627_10156084287820065_2425763806597329437_n.jpg

481 ms

12717162_514277878760231_1427692501729051532_n.jpg

12717162_514277878760231_1427692501729051532_n.jpg

481 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

74 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

74 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

70 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

69 ms

SEO Factors

foro-adelgazar.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ES

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foro-adelgazar.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed Spanish language. Our system also found out that Foro-adelgazar.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

foro-adelgazar.com

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