8.7 sec in total
2.5 sec
6 sec
132 ms
Visit facebook.poemse.com now to see the best up-to-date Facebook Poemse content for Iran and also check out these interesting facts you probably never knew about facebook.poemse.com
Visit facebook.poemse.comWe analyzed Facebook.poemse.com page load time and found that the first response time was 2.5 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
facebook.poemse.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value6.5 s
9/100
25%
Value8.4 s
18/100
10%
Value590 ms
50/100
30%
Value0.021
100/100
15%
Value9.3 s
32/100
10%
2544 ms
207 ms
211 ms
204 ms
203 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 94% of them (80 requests) were addressed to the original Facebook.poemse.com, 4% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Facebook.poemse.com.
Page size can be reduced by 177.7 kB (53%)
337.2 kB
159.5 kB
In fact, the total size of Facebook.poemse.com main page is 337.2 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. Javascripts take 184.8 kB which makes up the majority of the site volume.
Potential reduce by 22.2 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 22.2 kB or 75% of the original size.
Potential reduce by 10.9 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, Facebook Poemse needs image optimization as it can save up to 10.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.
Potential reduce by 125.5 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 125.5 kB or 68% of the original size.
Potential reduce by 19.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. Facebook.poemse.com needs all CSS files to be minified and compressed as it can save up to 19.1 kB or 81% of the original size.
Number of requests can be reduced by 22 (26%)
84
62
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facebook Poemse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
facebook.poemse.com
2544 ms
home-tw_90-04-16.css
207 ms
inside.js
211 ms
inside_autocomplete.js
204 ms
inside_postform.js
203 ms
inside_posts.js
199 ms
swfobject.js
200 ms
jquery.min.js
30 ms
popup.js
46 ms
cometchatcss.php
2005 ms
cometchatjs.php
3499 ms
analytics.js
37 ms
home_header_bg.gif
117 ms
new-user.png
136 ms
bb-signup.png
101 ms
mobile.png
139 ms
faq.jpg
194 ms
news.png
211 ms
export.png
232 ms
rss-all.png
234 ms
toggle_down_light.png
287 ms
keyboard.png
303 ms
new-logo.png
324 ms
home_search_btn.gif
325 ms
spacer.png
380 ms
home_search_type.gif
395 ms
home_search_input.gif
416 ms
online.png
417 ms
1455727268682763.png
473 ms
1448038893268160.png
489 ms
1440476413591856.png
510 ms
_noavatar_user.gif
515 ms
1456853699938578.png
589 ms
1406404577356069.png
589 ms
1453233271156703.png
602 ms
1455650492555484.png
611 ms
1456806046827669.png
683 ms
1456077707630132.png
684 ms
1456823050247583.png
695 ms
1436697085649326.png
704 ms
members.png
805 ms
1453730995802659.png
801 ms
1434512779871134.png
803 ms
1410206730363568.png
806 ms
1423475349150622.png
906 ms
1402688734872797.png
893 ms
collect
12 ms
1421680951764791.png
807 ms
1396190475749263.png
798 ms
1390127248836773.png
901 ms
1405177513599635.png
935 ms
1387618061468252.png
820 ms
1453838076408225.png
805 ms
1367513307564511.png
877 ms
1411413602738619.png
877 ms
1390509834432449.png
850 ms
1397474061837774.png
864 ms
groups.png
884 ms
1415977273732311.png
881 ms
_noavatar_group.gif
864 ms
1456507650872239.png
865 ms
1439410056957180.png
903 ms
1386350007448191.png
902 ms
1410867187232048.png
864 ms
1406933092241795.png
864 ms
1410333969459570.png
901 ms
1385919543258375.png
898 ms
1429044957230499.png
842 ms
1386271613414428.png
856 ms
1385713014968736.png
902 ms
1416761278803257.png
894 ms
1419884991439724.png
877 ms
1437925149736082.png
876 ms
1390671203101150.png
945 ms
1386146712722088.png
935 ms
1445782013234501.png
866 ms
advertise.png
871 ms
ttl.gif
925 ms
ttl2.gif
925 ms
2home.jpg
982 ms
Register.png
974 ms
login.png
1042 ms
advertisement.gif
948 ms
footer-border.png
856 ms
ga.js
12 ms
facebook.poemse.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
facebook.poemse.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
facebook.poemse.com SEO score
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
Document uses legible font sizes
FA
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facebook.poemse.com can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it matches the claimed language. Our system also found out that Facebook.poemse.com 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.
facebook.poemse.com
Open Graph description is not detected on the main page of Facebook Poemse. 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: