Tools & Wizards About Us
poeticterminology.net screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

poeticterminology.net

Types of Poetry

Page Load Speed

2.7 sec in total

First Response

260 ms

Resources Loaded

2.4 sec

Page Rendered

74 ms

poeticterminology.net screenshot

About Website

Welcome to poeticterminology.net homepage info - get ready to check Poeticterminology best content for Philippines right away, or after learning these important things about poeticterminology.net

Visit this comprehensive resource for definitions and examples of Types of Poetry. Facts and information and how to define different Types of Poetry. Examples and different Types of Poetry including s...

Visit poeticterminology.net

Key Findings

We analyzed Poeticterminology.net page load time and found that the first response time was 260 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

poeticterminology.net performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

poeticterminology.net

260 ms

www.poeticterminology.net

233 ms

consent.js

98 ms

analytics.js

28 ms

pubcode.min.js

106 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Poeticterminology.net, 19% (23 requests) were made to Router.infolinks.com and 10% (12 requests) were made to Simage2.pubmatic.com. The less responsive or slowest element that took the longest time to load (546 ms) relates to the external source T.adx.opera.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.9 kB (27%)

Content Size

268.7 kB

After Optimization

195.8 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-77%

Potential reduce by 34.0 kB

  • Original 43.9 kB
  • After minification 42.9 kB
  • After compression 9.9 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 34.0 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 520 B
  • After minification 520 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. Poeticterminology images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 38.9 kB

  • Original 224.3 kB
  • After minification 224.3 kB
  • After compression 185.4 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 38.9 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (77%)

Requests Now

91

After Optimization

21

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

poeticterminology.net

poeticterminology.net

260 ms

www.poeticterminology.net

www.poeticterminology.net

233 ms

consent.js

consent.js

98 ms

analytics.js

analytics.js

28 ms

pubcode.min.js

pubcode.min.js

106 ms

adsbygoogle.js

adsbygoogle.js

111 ms

pubcode.min.js

pubcode.min.js

103 ms

infolinks_main.js

infolinks_main.js

62 ms

flowerbasket.gif

flowerbasket.gif

164 ms

bar.gif

bar.gif

165 ms

collect

collect

15 ms

collect

collect

37 ms

js

js

87 ms

jsonp

jsonp

34 ms

cookie_sync

cookie_sync

6 ms

ice.js

ice.js

21 ms

lcmanage

lcmanage

345 ms

gsd

gsd

47 ms

manage

manage

80 ms

doq.htm

doq.htm

82 ms

405 ms

cksync

cksync

535 ms

bubble.js

bubble.js

358 ms

container-4.0.html

container-4.0.html

350 ms

iqusync-1.30.min.js

iqusync-1.30.min.js

188 ms

ImgSync

ImgSync

46 ms

sthr-us

sthr-us

87 ms

iqm-us

iqm-us

72 ms

sonobi-usync

sonobi-usync

85 ms

eqv-us

eqv-us

104 ms

ImgSync

ImgSync

30 ms

pixel

pixel

140 ms

frwh-us

frwh-us

77 ms

mgid-us

mgid-us

86 ms

qc-usync

qc-usync

120 ms

sovrn-usync

sovrn-usync

107 ms

211 ms

imd-usync

imd-usync

103 ms

tplift

tplift

127 ms

usermatch

usermatch

56 ms

33a-usync

33a-usync

121 ms

0

0

133 ms

intag_incontent.js

intag_incontent.js

48 ms

ox-usync

ox-usync

170 ms

apn-usync

apn-usync

115 ms

ix-usync

ix-usync

108 ms

pixel

pixel

93 ms

getads.htm

getads.htm

387 ms

outh-usync

outh-usync

153 ms

zmn-usync

zmn-usync

80 ms

mnet-usync

mnet-usync

77 ms

pixel

pixel

44 ms

rum

rum

66 ms

dcm

dcm

55 ms

crum

crum

67 ms

crum

crum

64 ms

usermatchredir

usermatchredir

56 ms

pixel

pixel

27 ms

img

img

180 ms

ur-usync

ur-usync

175 ms

crum

crum

40 ms

ImgSync

ImgSync

29 ms

ImgSync

ImgSync

29 ms

disus

disus

40 ms

sync

sync

546 ms

generic

generic

57 ms

user_sync.html

user_sync.html

96 ms

usync.html

usync.html

56 ms

sync

sync

84 ms

match

match

74 ms

generic

generic

38 ms

RX-f5b4ac26-0290-486b-84ef-eba3605043ad-005

RX-f5b4ac26-0290-486b-84ef-eba3605043ad-005

34 ms

usync.js

usync.js

44 ms

match

match

56 ms

receive

receive

48 ms

PugMaster

PugMaster

36 ms

sync

sync

27 ms

pixel

pixel

84 ms

FZt5psomz79DGe~O1V5PkX7S8-NVJIdw0INR-k~Duu9c36GyIDyElf4y8fa2~-9InNSq4BCadyu-8tQSiIkaVleT~Yh8GI4ocNSeo4~API4DJEsYNIMg2sPMMXvjcckTUFy53ZYw3gzv35jSAchydRkSr2XFgqe-kzzlKTlv1VT7-TlAc0PcX7nFzbKlHypwbpU3AWUAJgUx%20BDDE1910-714C-4C88-8927-B4CC88849926&rnd=RND

FZt5psomz79DGe~O1V5PkX7S8-NVJIdw0INR-k~Duu9c36GyIDyElf4y8fa2~-9InNSq4BCadyu-8tQSiIkaVleT~Yh8GI4ocNSeo4~API4DJEsYNIMg2sPMMXvjcckTUFy53ZYw3gzv35jSAchydRkSr2XFgqe-kzzlKTlv1VT7-TlAc0PcX7nFzbKlHypwbpU3AWUAJgUx%20BDDE1910-714C-4C88-8927-B4CC88849926&rnd=RND

232 ms

xuid

xuid

35 ms

pubmatic

pubmatic

34 ms

generic

generic

34 ms

BDDE1910-714C-4C88-8927-B4CC88849926

BDDE1910-714C-4C88-8927-B4CC88849926

231 ms

dcm

dcm

45 ms

sn.ashx

sn.ashx

331 ms

sync

sync

98 ms

i.match

i.match

364 ms

usersync.aspx

usersync.aspx

285 ms

pubmatic

pubmatic

322 ms

match

match

116 ms

Pug

Pug

269 ms

Pug

Pug

164 ms

user_sync.html

user_sync.html

182 ms

Pug

Pug

229 ms

Pug

Pug

144 ms

Pug

Pug

155 ms

Pug

Pug

224 ms

usersync.aspx

usersync.aspx

232 ms

Pug

Pug

171 ms

match

match

75 ms

Pug

Pug

96 ms

Pug

Pug

79 ms

b9pj45k4

b9pj45k4

47 ms

Pug

Pug

45 ms

Pug

Pug

56 ms

Pug

Pug

44 ms

pixel

pixel

54 ms

pixel

pixel

54 ms

Pug

Pug

35 ms

pbmtc.gif

pbmtc.gif

28 ms

Pug

Pug

47 ms

Pug

Pug

48 ms

sn.ashx

sn.ashx

37 ms

match

match

29 ms

i.match

i.match

123 ms

Pug

Pug

21 ms

Pug

Pug

27 ms

Pug

Pug

14 ms

52164

52164

22 ms

Pug

Pug

8 ms

zeta-usync

zeta-usync

96 ms

Accessibility Review

poeticterminology.net accessibility score

90

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

poeticterminology.net best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

poeticterminology.net SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poeticterminology.net can be misinterpreted by Google and other search engines. Our service has detected that English 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 Poeticterminology.net main page’s claimed encoding is windows-1252. 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

poeticterminology.net

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