6.5 sec in total
237 ms
5.9 sec
294 ms
Visit potte.com now to see the best up-to-date Potte content and also check out these interesting facts you probably never knew about potte.com
Peter Otte is the lead developer and creative director of Peter Otte Productions. PHP Developer, SEO Services, and Wild Apricot Consulting.
Visit potte.comWe analyzed Potte.com page load time and found that the first response time was 237 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
potte.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value11.5 s
0/100
25%
Value15.1 s
1/100
10%
Value3,540 ms
1/100
30%
Value0.463
19/100
15%
Value14.2 s
9/100
10%
237 ms
1782 ms
173 ms
211 ms
209 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Potte.com, 84% (72 requests) were made to Popsb.com and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Popsb.com.
Page size can be reduced by 508.8 kB (68%)
751.0 kB
242.3 kB
In fact, the total size of Potte.com main page is 751.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. 50% of websites need less resources to load. Javascripts take 426.8 kB which makes up the majority of the site volume.
Potential reduce by 66.3 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. This page needs HTML code to be minified as it can gain 14.4 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 66.3 kB or 82% of the original size.
Potential reduce by 3.9 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. Potte images are well optimized though.
Potential reduce by 277.7 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 277.7 kB or 65% of the original size.
Potential reduce by 160.9 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. Potte.com needs all CSS files to be minified and compressed as it can save up to 160.9 kB or 81% of the original size.
Number of requests can be reduced by 38 (49%)
78
40
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Potte. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
potte.com
237 ms
www.popsb.com
1782 ms
main.css
173 ms
skin.css
211 ms
styles.css
209 ms
mtw-style.css
229 ms
settings.css
229 ms
css
25 ms
colorbox.css
310 ms
jquery.js
412 ms
jquery-migrate.min.js
361 ms
jquery.jcarousel.min.js
363 ms
jquery.jj_ngg_shuffle.js
363 ms
jquery.themepunch.tools.min.js
435 ms
jquery.themepunch.revolution.min.js
448 ms
trigger_buttons.min.css
512 ms
jquery.fancybox-1.3.4.min.css
513 ms
font-awesome.min.css
514 ms
nextgen_basic_thumbnails.min.css
545 ms
style.min.css
574 ms
public.css
660 ms
flexslider.css
661 ms
seal.js
222 ms
jquery.colorbox-min.js
734 ms
jquery.form.min.js
734 ms
scripts.js
736 ms
wp-embed.min.js
739 ms
jquery.flexslider-min.js
797 ms
jQuery.easing.min.js
808 ms
ajax.min.js
766 ms
common.min.js
777 ms
nextgen_basic_thumbnails.min.js
815 ms
lightbox_context.min.js
819 ms
jquery.easing-1.3.pack.js
877 ms
jquery.fancybox-1.3.4.pack.js
889 ms
nextgen_fancybox_init.min.js
899 ms
ajax_pagination.min.js
909 ms
ga.js
28 ms
wp-emoji-release.min.js
822 ms
__utm.gif
13 ms
collect
48 ms
logotype.png
938 ms
DevThumb.jpg
937 ms
banksThumb-164x108.jpg
938 ms
info-thumb2-164x108.png
939 ms
IsabellaWeb-164x108.jpg
939 ms
home-thumb-2.jpg
939 ms
home-thumb-51.jpg
940 ms
home-thumb-32.jpg
939 ms
branding-320x440.jpg
940 ms
custom_dev-320x440.jpg
940 ms
graphic_design-320x440.jpg
941 ms
banks_slide-320x440.jpg
940 ms
web_solutions-320x440.jpg
981 ms
4b1f8059df24ec5d31f49b0d6f22a352
63 ms
blue-seal-63-134-peter-otte-productions-llc-92005791.png
89 ms
header-bg.jpg
719 ms
home-btn-hover.png
754 ms
menu-icon.png
765 ms
search-btn.png
774 ms
search-bar.png
859 ms
content-bg.gif
861 ms
main-slider-bg.gif
906 ms
preview-sidebar-bg.jpg
850 ms
arrow-thumb.gif
853 ms
quot-icon.gif
853 ms
seal_image.php
145 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
7 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
7 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
11 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
10 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
10 ms
helveticaneue-italic-webfont.woff
1045 ms
quot-small-icon.gif
947 ms
design-notes-title.png
921 ms
read-more.png
911 ms
twitter-icon.gif
898 ms
facebook-icon.png
910 ms
in-icon.gif
958 ms
bbb-logo.jpg
1003 ms
signup-btn.png
945 ms
border1.png
891 ms
border2.png
892 ms
main_mobile.css
162 ms
menu_responsive.js
138 ms
main.js
139 ms
potte.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
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
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
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
potte.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
potte.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Potte.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 Potte.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.
potte.com
Open Graph description is not detected on the main page of Potte. 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: