Tools & Wizards About Us

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

pur.at

LINK.at

Page Load Speed

2.6 sec in total

First Response

440 ms

Resources Loaded

2 sec

Page Rendered

78 ms

About Website

Welcome to pur.at homepage info - get ready to check Pur best content right away, or after learning these important things about pur.at

Php-X-Links is a links storage system to keep all your favorite links in one place no matter where you are

Visit pur.at

Key Findings

We analyzed Pur.at page load time and found that the first response time was 440 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

pur.at performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value4.4 s

73/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

pur.at

440 ms

link.pur.at

332 ms

home.html

352 ms

java.js

338 ms

show_ads.js

67 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Pur.at, 41% (13 requests) were made to Link.pur.at and 31% (10 requests) were made to Ifo.at. The less responsive or slowest element that took the longest time to load (451 ms) relates to the external source Link.pur.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.8 kB (36%)

Content Size

457.5 kB

After Optimization

292.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Pur.at main page is 457.5 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. Only 10% of websites need less resources to load. Javascripts take 394.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 29.7 kB

  • Original 37.2 kB
  • After minification 30.7 kB
  • After compression 7.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 6.5 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 29.7 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 25.4 kB
  • After minification 25.4 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. Pur images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 135.1 kB

  • Original 394.8 kB
  • After minification 390.9 kB
  • After compression 259.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 135.1 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (75%)

Requests Now

16

After Optimization

4

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

Accessibility Review

pur.at accessibility score

64

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

pur.at 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

pur.at 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

    DE

  • Language Claimed

    DE

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pur.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Pur.at 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

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