Tools & Wizards About Us
pokket.com screenshot

Report Summary

  • 0

    Performance

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

pokket.com

Pokket Pro | Home

Page Load Speed

400 ms in total

First Response

34 ms

Resources Loaded

200 ms

Page Rendered

166 ms

pokket.com screenshot

About Website

Welcome to pokket.com homepage info - get ready to check Pokket best content for United States right away, or after learning these important things about pokket.com

Pokket Pro

Visit pokket.com

Key Findings

We analyzed Pokket.com page load time and found that the first response time was 34 ms and then it took 366 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

pokket.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

pokket.com

34 ms

pokket.com

31 ms

b2d870a07928bab2.css

8 ms

polyfills-5cd94c89d3acac5f.js

14 ms

webpack-a87ea1fdc8d292cb.js

33 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 68% of them (15 requests) were addressed to the original Pokket.com, 27% (6 requests) were made to Fonts.gstatic.com and 5% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (78 ms) relates to the external source Fonts.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.9 kB (71%)

Content Size

74.6 kB

After Optimization

21.7 kB

  • HTML

In fact, the total size of Pokket.com main page is 74.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. 55% of websites need less resources to load. HTML takes 74.6 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 52.9 kB

  • Original 74.6 kB
  • After minification 74.6 kB
  • After compression 21.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 52.9 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (79%)

Requests Now

14

After Optimization

3

  • JavaScript
  • CSS

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

Network Requests Diagram

pokket.com

pokket.com

34 ms

pokket.com

pokket.com

31 ms

b2d870a07928bab2.css

b2d870a07928bab2.css

8 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

14 ms

webpack-a87ea1fdc8d292cb.js

webpack-a87ea1fdc8d292cb.js

33 ms

framework-bb5c596eafb42b22.js

framework-bb5c596eafb42b22.js

36 ms

main-9dfc16de60fa4c03.js

main-9dfc16de60fa4c03.js

33 ms

_app-f2aeb00cfe1ca2ce.js

_app-f2aeb00cfe1ca2ce.js

63 ms

675-843efb461bdfc57b.js

675-843efb461bdfc57b.js

34 ms

128-a34c6e62f809ccb2.js

128-a34c6e62f809ccb2.js

33 ms

690-da4c019b00fca702.js

690-da4c019b00fca702.js

62 ms

index-733d9191fcba57a9.js

index-733d9191fcba57a9.js

62 ms

_buildManifest.js

_buildManifest.js

68 ms

_ssgManifest.js

_ssgManifest.js

68 ms

_middlewareManifest.js

_middlewareManifest.js

69 ms

css2

css2

78 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

20 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

27 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

33 ms

pxiByp8kv8JHgFVrLFj_V1s.ttf

pxiByp8kv8JHgFVrLFj_V1s.ttf

37 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

37 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

36 ms

Accessibility Review

pokket.com accessibility score

81

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

pokket.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

pokket.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Pokket.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 Pokket.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

pokket.com

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