Tools & Wizards About Us
pag.es screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

pag.es

Geniuslink - URL Shortener for Creators and Affiliates

Page Load Speed

816 ms in total

First Response

41 ms

Resources Loaded

421 ms

Page Rendered

354 ms

pag.es screenshot

About Website

Click here to check amazing Pag content. Otherwise, check out these important facts you probably never knew about pag.es

Geniuslink is the world’s most intelligent URL shortener. Create links that dynamically route users to different destinations based off their devices, operating systems, countries, and even date of cl...

Visit pag.es

Key Findings

We analyzed Pag.es page load time and found that the first response time was 41 ms and then it took 775 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

pag.es performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

pag.es

41 ms

geniuslink.com

76 ms

main.css

23 ms

built.js

128 ms

cookieControl-9.2.1.min.js

59 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Pag.es, 90% (19 requests) were made to Geniuslink.com and 5% (1 request) were made to Cc.cdn.civiccomputing.com. The less responsive or slowest element that took the longest time to load (258 ms) relates to the external source Geniuslink.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 150.1 kB (23%)

Content Size

648.2 kB

After Optimization

498.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pag.es main page is 648.2 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. 40% of websites need less resources to load. Images take 367.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 22.1 kB

  • Original 29.3 kB
  • After minification 24.4 kB
  • After compression 7.2 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.9 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 22.1 kB or 75% of the original size.

Image Optimization

-26%

Potential reduce by 96.2 kB

  • Original 367.1 kB
  • After minification 271.0 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, Pag needs image optimization as it can save up to 96.2 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-11%

Potential reduce by 21.3 kB

  • Original 202.3 kB
  • After minification 202.3 kB
  • After compression 181.0 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 21.3 kB or 11% of the original size.

CSS Optimization

-21%

Potential reduce by 10.5 kB

  • Original 49.5 kB
  • After minification 49.5 kB
  • After compression 39.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. Pag.es needs all CSS files to be minified and compressed as it can save up to 10.5 kB or 21% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pag. According to our analytics all requests are already optimized.

Network Requests Diagram

pag.es

pag.es

41 ms

geniuslink.com

geniuslink.com

76 ms

main.css

main.css

23 ms

built.js

built.js

128 ms

cookieControl-9.2.1.min.js

cookieControl-9.2.1.min.js

59 ms

fancybox.umd.js

fancybox.umd.js

49 ms

close.png

close.png

12 ms

loading.gif

loading.gif

222 ms

prev.png

prev.png

224 ms

next.png

next.png

225 ms

geniuslink-logo-white-blue.svg

geniuslink-logo-white-blue.svg

223 ms

geniuslink-logo-white.svg

geniuslink-logo-white.svg

226 ms

hero-brain.svg

hero-brain.svg

230 ms

choice-collection.png

choice-collection.png

258 ms

artsm-intelligent.png

artsm-intelligent.png

229 ms

artsm-placeholder.png

artsm-placeholder.png

228 ms

privacy-participation.png

privacy-participation.png

228 ms

vsprites.svg

vsprites.svg

151 ms

client-logos-gray.png

client-logos-gray.png

173 ms

price-features-bg.jpg

price-features-bg.jpg

171 ms

uicons.png

uicons.png

171 ms

Accessibility Review

pag.es 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

pag.es best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pag.es SEO score

88

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pag.es 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 Pag.es 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.

Social Sharing Optimization

pag.es

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