3.6 sec in total
496 ms
2.7 sec
489 ms
Visit pollen.co now to see the best up-to-date Pollen content for United States and also check out these interesting facts you probably never knew about pollen.co
Get access to all of the best experiences in one place. Always get more by booking with Pollen.
Visit pollen.coWe analyzed Pollen.co page load time and found that the first response time was 496 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
pollen.co performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value5.3 s
21/100
25%
Value8.8 s
16/100
10%
Value1,980 ms
8/100
30%
Value0.005
100/100
15%
Value18.3 s
3/100
10%
496 ms
138 ms
70 ms
83 ms
128 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 71% of them (24 requests) were addressed to the original Pollen.co, 24% (8 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (706 ms) belongs to the original domain Pollen.co.
Page size can be reduced by 959.4 kB (21%)
4.6 MB
3.6 MB
In fact, the total size of Pollen.co main page is 4.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 27.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 27.8 kB or 77% of the original size.
Potential reduce by 546.8 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. Obviously, Pollen needs image optimization as it can save up to 546.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 242.8 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 242.8 kB or 69% of the original size.
Potential reduce by 142.0 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. Pollen.co needs all CSS files to be minified and compressed as it can save up to 142.0 kB or 87% of the original size.
Number of requests can be reduced by 14 (56%)
25
11
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pollen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.pollen.co
496 ms
reset.css
138 ms
css
70 ms
css
83 ms
style.css
128 ms
aqpb-view.css
133 ms
mediaelementplayer.min.css
201 ms
wp-mediaelement.css
146 ms
jquery.js
306 ms
jquery-migrate.min.js
192 ms
aqpb-view.js
129 ms
mediaelement-and-player.min.js
231 ms
wp-mediaelement.js
142 ms
scripts.min.js
314 ms
wp-embed.min.js
188 ms
styles.min.css
276 ms
wp-emoji-release.min.js
163 ms
Logo.png
130 ms
Cover-4.png
383 ms
Pollen_Web_Logo-1.png
129 ms
Gradient-e1457034190658.png
706 ms
Cover-photo.png
569 ms
Cover-Photo-2-1.png
563 ms
Cover-3.png
585 ms
Download-on-App-Store-1.png
239 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
159 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
173 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
174 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
173 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
175 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
176 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
174 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
174 ms
Footer.png
689 ms
pollen.co accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
pollen.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
pollen.co 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
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 Pollen.co 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 Pollen.co 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.
pollen.co
Open Graph description is not detected on the main page of Pollen. 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: