1.5 sec in total
416 ms
932 ms
172 ms
Visit poemish.com now to see the best up-to-date Poemish content for United States and also check out these interesting facts you probably never knew about poemish.com
Visit poemish.comWe analyzed Poemish.com page load time and found that the first response time was 416 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
poemish.com performance score
416 ms
6 ms
138 ms
52 ms
59 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 83% of them (39 requests) were addressed to the original Poemish.com, 6% (3 requests) were made to Staticxx.facebook.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (416 ms) belongs to the original domain Poemish.com.
Page size can be reduced by 170.5 kB (37%)
462.6 kB
292.2 kB
In fact, the total size of Poemish.com main page is 462.6 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. 25% of websites need less resources to load. Images take 211.2 kB which makes up the majority of the site volume.
Potential reduce by 16.7 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 16.7 kB or 71% of the original size.
Potential reduce by 900 B
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. Poemish images are well optimized though.
Potential reduce by 130.3 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 130.3 kB or 66% of the original size.
Potential reduce by 22.6 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. Poemish.com needs all CSS files to be minified and compressed as it can save up to 22.6 kB or 76% of the original size.
Number of requests can be reduced by 11 (24%)
46
35
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Poemish. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
poemish.com
416 ms
A.common.css.pagespeed.cf.SsRsDi05_Y.css
6 ms
common.js
138 ms
app.js.pagespeed.ce.3uefbWkyWb.js
52 ms
ga.js
59 ms
all.js
71 ms
bg_body17.jpg.pagespeed.ce.7TEMnj2qTF.jpg
110 ms
logo.png.pagespeed.ce.2eF-6zk01X.png
10 ms
xsearch.png.pagespeed.ic.txJPiolkHO.png
9 ms
bg_intro.png
123 ms
xalert-overlay.png.pagespeed.ic.7HAmKqrsoP.png
15 ms
x85897bb906d2a68ea30bb23c9ec6eae9271c8cc0.png.pagespeed.ic.dixVuLSihq.png
94 ms
x443985cb245802ee21bec3e055246fec2cfe734a.png.pagespeed.ic.RBuF1Lv8Y_.jpg
94 ms
x05ed53252250b4e92247b8d91ae1c93a84741809.png.pagespeed.ic.XVaMy3t31Z.jpg
12 ms
xa3050e3d416c7ab87f2cb8936ebebb8f3ca405f5.png.pagespeed.ic.8N1aILcV2o.png
14 ms
x5b4a1990ce60a9bb60890ba592d2a332fdd57a3d.png.pagespeed.ic.mCf2kBMSau.jpg
17 ms
x347f130171e210f1c462caccfd66d60083b0135e.png.pagespeed.ic._uVwOjNx2v.jpg
18 ms
xno_image_a.png.pagespeed.ic.to8_KCfNEj.png
21 ms
xavtar_fbdb74fb01bb07d9158ea9559f467a1a_small.png.pagespeed.ic.lv3m0GQS0U.jpg
23 ms
xavtar_1e9240aae68f7b36622c7308dc079fba_small.png.pagespeed.ic.qGR13UFvVT.jpg
23 ms
xavtar_41134b2fe630fc016e951a518e9a5762_small.png.pagespeed.ic.fQBRtafklC.png
25 ms
xno_image_b.png.pagespeed.ic.t5F9vGH0iJ.png
27 ms
xavtar_9054a99dc34e450c3b048bfdbd070200_small.png.pagespeed.ic.2Z6o8pa3MN.jpg
28 ms
xavtar_20321bba2afae249f2bc756a624fc9a9_small.png.pagespeed.ic.zTNyRgZFhe.jpg
30 ms
xavtar_6ac98bc409a1f843bfe68a8450dd7165_small.png.pagespeed.ic.FJFhCedD9b.jpg
31 ms
xno_image_c.png.pagespeed.ic.mjDpFHfhPM.png
49 ms
xno_image_d.png.pagespeed.ic.im6u6fh-If.png
50 ms
xavtar_a36ad1d6db8eca8068a9a5486e78d2c7_small.png.pagespeed.ic.Lj7LTl4gua.jpg
106 ms
xavtar_7daf3624ed4790d9970b3921b00088a7_small.png.pagespeed.ic.6FQJfKQ4in.jpg
50 ms
xno_image_e.png.pagespeed.ic.aAmcZu_f5v.png
101 ms
xavtar_28bcb48b18960ae8264612108f520453_small.png.pagespeed.ic.d-sUlhvGel.png
91 ms
xavtar_d6b3c5e6ae3586f8d54e1f449a02de8a_small.png.pagespeed.ic.Eor2agPDjz.jpg
91 ms
xavtar_e798c0d22cbcbf3a22f539c712900bf8_small.png.pagespeed.ic.WH1cXj802s.jpg
92 ms
xavtar_553fb1f6702f028295cd9271ad475924_small.png.pagespeed.ic.H3RQCBxJVG.jpg
93 ms
xavtar_29d12de1431e4747ab10ff79a82117ae_small.png.pagespeed.ic.U8LJDzj39O.jpg
140 ms
xavtar_43e0fd5dc94a7fd5cb254284c8714721_small.png.pagespeed.ic.pQUoCmmf50.jpg
93 ms
xavtar_eb472109b172221086daa313cb1085eb_small.png.pagespeed.ic.zna51151Yf.jpg
103 ms
xavtar_5f1759aa07bfbf4500c41c98f07822fd_small.png.pagespeed.ic.sbeFydgNre.jpg
103 ms
xavtar_11add001a7abe5f9363e11b5b8660573_small.png.pagespeed.ic.9RfAkyjhPB.jpg
138 ms
xavtar_5dc0599afa68bab5adfd711e983ce734_small.png.pagespeed.ic.NNuoGnLila.jpg
166 ms
xavtar_8a63bf40976c00bd50199f242399bbef_small.png.pagespeed.ic.jcawz32H9z.jpg
107 ms
943900_868802766552470_3474560570699140840_n.jpg
118 ms
__utm.gif
44 ms
129 ms
xd_arbiter.php
79 ms
xd_arbiter.php
135 ms
xd_arbiter.php
38 ms
poemish.com accessibility score
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
<frame> or <iframe> elements do not have a title
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
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.
poemish.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
poemish.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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poemish.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Poemish.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.
poemish.com
Open Graph description is not detected on the main page of Poemish. 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: