Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

pollenapps.com

National Allergy Forecast & Info About Allergies | Pollen.com

Page Load Speed

295 ms in total

First Response

102 ms

Resources Loaded

107 ms

Page Rendered

86 ms

pollenapps.com screenshot

About Website

Visit pollenapps.com now to see the best up-to-date Pollen Apps content for United States and also check out these interesting facts you probably never knew about pollenapps.com

Check out national allergy map, get your local allergy outlook, track you allergies with Allergy Diary, and more features at Pollen.com

Visit pollenapps.com

Key Findings

We analyzed Pollenapps.com page load time and found that the first response time was 102 ms and then it took 193 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

pollenapps.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value17.4 s

0/100

10%

TBT (Total Blocking Time)

Value41,880 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.123

83/100

15%

TTI (Time to Interactive)

Value54.2 s

0/100

10%

Network Requests Diagram

pollenapps.com

102 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Pollenapps.com and no external sources were called. The less responsive or slowest element that took the longest time to load (102 ms) belongs to the original domain Pollenapps.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 102 B (41%)

Content Size

250 B

After Optimization

148 B

In fact, the total size of Pollenapps.com main page is 250 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 250 B which makes up the majority of the site volume.

HTML Optimization

-41%

Potential reduce by 102 B

  • Original 250 B
  • After minification 243 B
  • After compression 148 B

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 102 B or 41% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

pollenapps.com accessibility score

76

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

High

Image elements do not have [alt] attributes

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.

Best Practices

pollenapps.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

pollenapps.com SEO score

89

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pollenapps.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pollenapps.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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