1.3 sec in total
87 ms
867 ms
301 ms
Click here to check amazing Poke Card content for United States. Otherwise, check out these important facts you probably never knew about pokecard.net
Pokemon Card Maker lets you make realistic looking Pokemon cards quickly and easily!
Visit pokecard.netWe analyzed Pokecard.net page load time and found that the first response time was 87 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
pokecard.net performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value3.7 s
57/100
25%
Value5.3 s
57/100
10%
Value2,340 ms
5/100
30%
Value0
100/100
15%
Value12.9 s
13/100
10%
87 ms
127 ms
207 ms
107 ms
31 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 23% of them (13 requests) were addressed to the original Pokecard.net, 40% (23 requests) were made to Forum.pokecard.net and 7% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (254 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 56.3 kB (10%)
575.9 kB
519.5 kB
In fact, the total size of Pokecard.net main page is 575.9 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. 60% of websites need less resources to load. Images take 328.0 kB which makes up the majority of the site volume.
Potential reduce by 32.8 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 32.8 kB or 75% of the original size.
Potential reduce by 21.1 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. Poke Card images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 70 B
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. Pokecard.net has all CSS files already compressed.
Number of requests can be reduced by 28 (53%)
53
25
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Poke Card. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
pokecard.net
87 ms
www.pokecard.net
127 ms
cloudflare.min.js
207 ms
index.php
107 ms
jquery.min.js
31 ms
cookie.js
98 ms
ipbforumskins.js
98 ms
index.php
127 ms
index.php
125 ms
adsbygoogle.js
6 ms
jquery.min.js
72 ms
element.js
70 ms
ga.js
54 ms
translateelement.css
157 ms
main.js
163 ms
fire.png
24 ms
grass.png
25 ms
water.png
29 ms
lightning.png
25 ms
psychic.png
30 ms
fighting.png
27 ms
colorless.png
24 ms
steel.png
25 ms
dark.png
27 ms
createcard.jpg
78 ms
background.jpg
77 ms
6_logo.png
77 ms
advanced_search.png
31 ms
highlight.png
30 ms
search_icon.png
76 ms
facebook.png
76 ms
user_login.png
78 ms
user_register.png
77 ms
secondary_nav_bg.png
89 ms
secondary_nav.png
90 ms
icon_quicknav.png
89 ms
top.png
88 ms
feed.png
89 ms
ca-pub-5457154328841199.js
140 ms
zrt_lookup.html
142 ms
show_ads_impl.js
81 ms
__utm.gif
22 ms
ads
250 ms
all.js
88 ms
maintitle.png
35 ms
header_left.png
36 ms
header_right.png
35 ms
highlight_strong.png
34 ms
osd.js
33 ms
element_main.js
56 ms
ads
254 ms
highlight_faint.png
34 ms
ads
251 ms
actions.php
105 ms
168 ms
xd_arbiter.php
67 ms
xd_arbiter.php
146 ms
pokecard.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Form elements do not have associated labels
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.
pokecard.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
pokecard.net 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pokecard.net 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 Pokecard.net 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.
pokecard.net
Open Graph description is not detected on the main page of Poke Card. 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: