Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

apresparty.com

Après Event Décor and Tent Rental - Party, Wedding and Tent Rentals in Minnetonka, Minnesota

Page Load Speed

1.4 sec in total

First Response

92 ms

Resources Loaded

839 ms

Page Rendered

459 ms

apresparty.com screenshot

About Website

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

Visit apresparty.com

Key Findings

We analyzed Apresparty.com page load time and found that the first response time was 92 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

apresparty.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.378

28/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

apresparty.com

92 ms

apresparty.com

194 ms

jquery.min.js

36 ms

css2

49 ms

css2

60 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 67% of them (33 requests) were addressed to the original Apresparty.com, 16% (8 requests) were made to Scontent-mty2-1.cdninstagram.com and 8% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (321 ms) relates to the external source Scontent-mty2-1.cdninstagram.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 331.3 kB (29%)

Content Size

1.2 MB

After Optimization

829.6 kB

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

HTML Optimization

-78%

Potential reduce by 24.7 kB

  • Original 31.8 kB
  • After minification 25.8 kB
  • After compression 7.1 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 5.9 kB, which is 19% 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 24.7 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 14.5 kB

  • Original 739.2 kB
  • After minification 724.6 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. Apres Party images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 56.0 kB

  • Original 126.7 kB
  • After minification 110.6 kB
  • After compression 70.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 56.0 kB or 44% of the original size.

CSS Optimization

-90%

Potential reduce by 236.1 kB

  • Original 263.3 kB
  • After minification 156.9 kB
  • After compression 27.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. Apresparty.com needs all CSS files to be minified and compressed as it can save up to 236.1 kB or 90% of the original size.

Requests Breakdown

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

Requests Now

39

After Optimization

18

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

Accessibility Review

apresparty.com accessibility score

48

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.

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

apresparty.com best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

apresparty.com SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

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