Tools & Wizards About Us
figures.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

figures.com

Figures.com | All The Toy And Action Figure News All The Time

Page Load Speed

1.6 sec in total

First Response

182 ms

Resources Loaded

1.2 sec

Page Rendered

249 ms

figures.com screenshot

About Website

Click here to check amazing Figures content for United States. Otherwise, check out these important facts you probably never knew about figures.com

Visit figures.com

Key Findings

We analyzed Figures.com page load time and found that the first response time was 182 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

figures.com performance score

0

Network Requests Diagram

figures.com

182 ms

www.figures.com

212 ms

common.css

88 ms

rssdisplaybox.css

91 ms

virtualpaginate.js

91 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 53% of them (40 requests) were addressed to the original Figures.com, 39% (29 requests) were made to Ads2.figures.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (656 ms) relates to the external source Ads2.figures.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.3 kB (28%)

Content Size

289.7 kB

After Optimization

208.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Figures.com main page is 289.7 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. 35% of websites need less resources to load. Images take 190.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 23.2 kB

  • Original 28.7 kB
  • After minification 25.9 kB
  • After compression 5.5 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 23.2 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 15.9 kB

  • Original 190.9 kB
  • After minification 175.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. Figures images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 21.7 kB

  • Original 45.6 kB
  • After minification 35.3 kB
  • After compression 24.0 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 21.7 kB or 47% of the original size.

CSS Optimization

-84%

Potential reduce by 20.5 kB

  • Original 24.5 kB
  • After minification 14.9 kB
  • After compression 4.0 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. Figures.com needs all CSS files to be minified and compressed as it can save up to 20.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (38%)

Requests Now

72

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

figures.com

figures.com

182 ms

www.figures.com

www.figures.com

212 ms

common.css

common.css

88 ms

rssdisplaybox.css

rssdisplaybox.css

91 ms

virtualpaginate.js

virtualpaginate.js

91 ms

rssdisplaybox.js

rssdisplaybox.js

91 ms

jsapi

jsapi

18 ms

misc.js

misc.js

95 ms

tools.flashembed-1.0.4.min.js

tools.flashembed-1.0.4.min.js

95 ms

jquery.min.js

jquery.min.js

33 ms

embed.js

embed.js

209 ms

JsTracker.aspx

JsTracker.aspx

129 ms

4f2db061991520241a838c85e0d87aec.gif

4f2db061991520241a838c85e0d87aec.gif

656 ms

lg.php

lg.php

168 ms

6c2a4070ecfd44ecf77a0d77d7f6680c.jpg

6c2a4070ecfd44ecf77a0d77d7f6680c.jpg

169 ms

lg.php

lg.php

164 ms

5e0f7832a3a5a228a8008758f62be6f8.gif

5e0f7832a3a5a228a8008758f62be6f8.gif

211 ms

lg.php

lg.php

164 ms

828993735d2b1869677442d8e4aad0b3.gif

828993735d2b1869677442d8e4aad0b3.gif

266 ms

lg.php

lg.php

248 ms

8acd1a86e2a7be604aee40da8ea696fd.gif

8acd1a86e2a7be604aee40da8ea696fd.gif

316 ms

lg.php

lg.php

271 ms

dff79033cdde95d3dc454eb60cb13a35.jpg

dff79033cdde95d3dc454eb60cb13a35.jpg

291 ms

lg.php

lg.php

341 ms

606776c3539a840786e17574c8c361c2.gif

606776c3539a840786e17574c8c361c2.gif

361 ms

lg.php

lg.php

375 ms

d25e4a6714afe4adb53bfd71cb809ee7.jpg

d25e4a6714afe4adb53bfd71cb809ee7.jpg

371 ms

lg.php

lg.php

418 ms

4974e89abb9471b33028d7edab8ec80e.gif

4974e89abb9471b33028d7edab8ec80e.gif

420 ms

lg.php

lg.php

465 ms

d6af84edc1d8cc71f010cdd88b30aee9.gif

d6af84edc1d8cc71f010cdd88b30aee9.gif

453 ms

lg.php

lg.php

467 ms

72bd220b466aa9bcb6819b31e4604489.gif

72bd220b466aa9bcb6819b31e4604489.gif

497 ms

lg.php

lg.php

513 ms

09c3f29f6aa8da7e97b89343e1a5dfbb.gif

09c3f29f6aa8da7e97b89343e1a5dfbb.gif

533 ms

lg.php

lg.php

555 ms

76d93a5157673f486a3771605eac43aa.gif

76d93a5157673f486a3771605eac43aa.gif

624 ms

lg.php

lg.php

586 ms

b95cf98ad5be341000eab02764264e48.gif

b95cf98ad5be341000eab02764264e48.gif

634 ms

lg.php

lg.php

628 ms

lg.php

lg.php

649 ms

mastheadBack.png

mastheadBack.png

85 ms

figuresLogo.png

figuresLogo.png

102 ms

navback1.png

navback1.png

104 ms

navbackLit.png

navbackLit.png

104 ms

navbackLit-b.png

navbackLit-b.png

103 ms

nav-lowcap2.gif

nav-lowcap2.gif

166 ms

navNetworkBack.png

navNetworkBack.png

168 ms

none

none

169 ms

rss.png

rss.png

177 ms

f_logo.png

f_logo.png

179 ms

t_logo.png

t_logo.png

179 ms

mainContainerBack.png

mainContainerBack.png

250 ms

contentOuterHeadBack.png

contentOuterHeadBack.png

251 ms

contentHeadTopNews.png

contentHeadTopNews.png

252 ms

contentOuterHeadMain.png

contentOuterHeadMain.png

252 ms

attachment.php

attachment.php

301 ms

attachment.php

attachment.php

304 ms

attachment.php

attachment.php

383 ms

attachment.php

attachment.php

381 ms

attachment.php

attachment.php

395 ms

attachment.php

attachment.php

392 ms

attachment.php

attachment.php

433 ms

attachment.php

attachment.php

427 ms

attachment.php

attachment.php

507 ms

attachment.php

attachment.php

513 ms

attachment.php

attachment.php

534 ms

attachment.php

attachment.php

541 ms

attachment.php

attachment.php

562 ms

attachment.php

attachment.php

555 ms

ga.js

ga.js

30 ms

rssBoxHeadRed.png

rssBoxHeadRed.png

494 ms

footer-background01.png

footer-background01.png

539 ms

__utm.gif

__utm.gif

12 ms

300093_120x120.gif

300093_120x120.gif

13 ms

SEO Factors

figures.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

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

figures.com

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