Tools & Wizards About Us
podictionary.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

podictionary.com

podictionary - for word lovers - daily stories, trivia & dictionary etymology

Page Load Speed

6.5 sec in total

First Response

71 ms

Resources Loaded

4.8 sec

Page Rendered

1.6 sec

podictionary.com screenshot

About Website

Welcome to podictionary.com homepage info - get ready to check Po Dictionary best content right away, or after learning these important things about podictionary.com

All hotels in Buenos Aires. The best selection of Buenos Aires hotels with reviews and maps. Book in advance and save.

Visit podictionary.com

Key Findings

We analyzed Podictionary.com page load time and found that the first response time was 71 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

podictionary.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

65/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

podictionary.com

71 ms

podictionary.html

241 ms

common-d80d0ea0e8.pack.css

21 ms

dtheme5-d427cb4146.pack.css

53 ms

vendors-5ca5b034aa.pack.js

89 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Podictionary.com, 58% (28 requests) were made to Web.archive.org and 31% (15 requests) were made to Pennsylvaniahotels24.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Web.archive.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 232.8 kB (24%)

Content Size

957.0 kB

After Optimization

724.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Podictionary.com main page is 957.0 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. Images take 722.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 117.0 kB

  • Original 146.0 kB
  • After minification 144.7 kB
  • After compression 29.0 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 117.0 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 62.8 kB

  • Original 722.8 kB
  • After minification 660.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. Po Dictionary images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-75%

Potential reduce by 52.9 kB

  • Original 71.0 kB
  • After minification 71.0 kB
  • After compression 18.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. Podictionary.com needs all CSS files to be minified and compressed as it can save up to 52.9 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (15%)

Requests Now

46

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

podictionary.com

podictionary.com

71 ms

podictionary.html

podictionary.html

241 ms

common-d80d0ea0e8.pack.css

common-d80d0ea0e8.pack.css

21 ms

dtheme5-d427cb4146.pack.css

dtheme5-d427cb4146.pack.css

53 ms

vendors-5ca5b034aa.pack.js

vendors-5ca5b034aa.pack.js

89 ms

app-db86495914.pack.js

app-db86495914.pack.js

196 ms

_.gif

_.gif

218 ms

pennsylvaniahotels24.com.jpg

pennsylvaniahotels24.com.jpg

200 ms

logo.jpg

logo.jpg

247 ms

icn-91c0d80610.png

icn-91c0d80610.png

289 ms

spacer.gif

spacer.gif

338 ms

thawte-5e81a46033.gif

thawte-5e81a46033.gif

386 ms

close.png

close.png

439 ms

loading.gif

loading.gif

486 ms

prev.png

prev.png

534 ms

next-80bfdf94f6.png

next-80bfdf94f6.png

585 ms

ga.js

ga.js

21 ms

staticmap

staticmap

160 ms

css

css

37 ms

CK3D.jpg

CK3D.jpg

1176 ms

__utm.gif

__utm.gif

11 ms

bewilder.jpg

bewilder.jpg

1147 ms

iconfiled.gif

iconfiled.gif

1177 ms

iconcomment.gif

iconcomment.gif

1169 ms

nest.jpg

nest.jpg

1278 ms

icondate.gif

icondate.gif

1230 ms

chrome-math.jpg

chrome-math.jpg

1325 ms

GG-book.jpg

GG-book.jpg

1543 ms

chrome-gun.jpg

chrome-gun.jpg

1137 ms

chrome-Google.jpg

chrome-Google.jpg

1193 ms

Tabasco-1.jpg

Tabasco-1.jpg

1309 ms

switch-whip.jpg

switch-whip.jpg

1197 ms

Tabasco-drink.jpg

Tabasco-drink.jpg

1226 ms

niche.jpg

niche.jpg

1409 ms

switch-1.jpg

switch-1.jpg

2401 ms

bluff-game.PNG

bluff-game.PNG

1456 ms

bluff-cards.jpg

bluff-cards.jpg

1657 ms

buff-girl.jpg

buff-girl.jpg

1797 ms

GW-cover-s.JPG

GW-cover-s.JPG

1536 ms

itunes-sml.gif

itunes-sml.gif

1599 ms

cushy-grave.jpg

cushy-grave.jpg

1287 ms

buff-boy.jpg

buff-boy.jpg

3338 ms

cushy-chair.jpg

cushy-chair.jpg

1762 ms

thug.jpg

thug.jpg

1422 ms

Samuel_Johnson.png

Samuel_Johnson.png

1967 ms

thug-kali.jpg

thug-kali.jpg

1665 ms

complainee-roed.jpg

complainee-roed.jpg

1628 ms

favicon.ico

favicon.ico

1952 ms

Accessibility Review

podictionary.com accessibility score

67

Accessibility Issues

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

High

Buttons do not have an accessible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

podictionary.com best practices score

83

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

SEO Factors

podictionary.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Podictionary.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 Podictionary.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.

Social Sharing Optimization

podictionary.com

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