Tools & Wizards About Us
pergenex.com screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

pergenex.com

Better Outlook Rules | Outlook Add-in Software by Pergenex Software

Page Load Speed

516 ms in total

First Response

100 ms

Resources Loaded

295 ms

Page Rendered

121 ms

pergenex.com screenshot

About Website

Click here to check amazing Pergenex content for United States. Otherwise, check out these important facts you probably never knew about pergenex.com

Pergenex Software - publisher of add-in software for Microsoft Outlook and Exchange to help organize and automate your inbox.

Visit pergenex.com

Key Findings

We analyzed Pergenex.com page load time and found that the first response time was 100 ms and then it took 416 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

pergenex.com performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

pergenex.com

100 ms

styles.css

20 ms

default.css

7 ms

jsapi

10 ms

loader.js

29 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 72% of them (33 requests) were addressed to the original Pergenex.com, 15% (7 requests) were made to Google.com and 4% (2 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (137 ms) belongs to the original domain Pergenex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 54.0 kB (12%)

Content Size

452.9 kB

After Optimization

398.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pergenex.com main page is 452.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. 35% of websites need less resources to load. Javascripts take 211.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 18.7 kB

  • Original 24.2 kB
  • After minification 20.2 kB
  • After compression 5.6 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 4.1 kB, which is 17% 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 18.7 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 7.6 kB

  • Original 195.4 kB
  • After minification 187.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. Pergenex images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 15.0 kB

  • Original 211.4 kB
  • After minification 211.4 kB
  • After compression 196.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.

CSS Optimization

-58%

Potential reduce by 12.7 kB

  • Original 21.9 kB
  • After minification 20.0 kB
  • After compression 9.2 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. Pergenex.com needs all CSS files to be minified and compressed as it can save up to 12.7 kB or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (49%)

Requests Now

43

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pergenex.com

pergenex.com

100 ms

styles.css

styles.css

20 ms

default.css

default.css

7 ms

jsapi

jsapi

10 ms

loader.js

loader.js

29 ms

quant.js

quant.js

13 ms

1pxpgback.jpg

1pxpgback.jpg

15 ms

cse.js

cse.js

72 ms

ga.js

ga.js

11 ms

pergenex-logo.jpg

pergenex-logo.jpg

46 ms

head1.jpg

head1.jpg

45 ms

head2.jpg

head2.jpg

62 ms

nav-back.jpg

nav-back.jpg

66 ms

arrv_white_1.gif

arrv_white_1.gif

54 ms

1gradiant.jpg

1gradiant.jpg

135 ms

index_14.jpg

index_14.jpg

84 ms

index_16.jpg

index_16.jpg

70 ms

index_17.jpg

index_17.jpg

69 ms

index_19-1.jpg

index_19-1.jpg

73 ms

pg-tit.jpg

pg-tit.jpg

80 ms

index_42.jpg

index_42.jpg

83 ms

index_52.jpg

index_52.jpg

81 ms

head-back.jpg

head-back.jpg

85 ms

index_55.jpg

index_55.jpg

129 ms

Auto-Mate-Pro-box-sm.jpg

Auto-Mate-Pro-box-sm.jpg

134 ms

pg-head.jpg

pg-head.jpg

130 ms

index_66.jpg

index_66.jpg

129 ms

read-more.jpg

read-more.jpg

133 ms

MessageAssist-box-sm.jpg

MessageAssist-box-sm.jpg

134 ms

spacer.gif

spacer.gif

136 ms

index_40.jpg

index_40.jpg

133 ms

index_43.jpg

index_43.jpg

134 ms

right-head.jpg

right-head.jpg

135 ms

hline-right.jpg

hline-right.jpg

135 ms

read-more1.jpg

read-more1.jpg

136 ms

index_83.jpg

index_83.jpg

136 ms

index_87.jpg

index_87.jpg

136 ms

index_92.jpg

index_92.jpg

137 ms

copyright.jpg

copyright.jpg

137 ms

__utm.gif

__utm.gif

11 ms

cse_element__en.js

cse_element__en.js

20 ms

default+en.css

default+en.css

60 ms

default.css

default.css

63 ms

async-ads.js

async-ads.js

29 ms

branding.png

branding.png

15 ms

clear.png

clear.png

10 ms

Accessibility Review

pergenex.com accessibility score

84

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

pergenex.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pergenex.com SEO score

69

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pergenex.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 Pergenex.com main page’s claimed encoding is iso-8859-1. 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

pergenex.com

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