Tools & Wizards About Us
uglyparis.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

Page Load Speed

4.8 sec in total

First Response

573 ms

Resources Loaded

3.8 sec

Page Rendered

491 ms

uglyparis.com screenshot

About Website

Visit uglyparis.com now to see the best up-to-date Uglyparis content and also check out these interesting facts you probably never knew about uglyparis.com

Visit uglyparis.com

Key Findings

We analyzed Uglyparis.com page load time and found that the first response time was 573 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

uglyparis.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value2,110 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

Network Requests Diagram

uglyparis.com

573 ms

www.uglyparis.com

700 ms

styles.css

668 ms

0.jpg

302 ms

0.gif

907 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 88% of them (22 requests) were addressed to the original Uglyparis.com, 4% (1 request) were made to Www16.moba8.net and 4% (1 request) were made to Www17.a8.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Uglyparis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 31.2 kB (24%)

Content Size

129.6 kB

After Optimization

98.5 kB

  • HTML
  • Images
  • CSS

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

HTML Optimization

-64%

Potential reduce by 6.8 kB

  • Original 10.6 kB
  • After minification 10.6 kB
  • After compression 3.9 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. 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 6.8 kB or 64% of the original size.

Image Optimization

-2%

Potential reduce by 1.7 kB

  • Original 91.5 kB
  • After minification 89.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. Uglyparis images are well optimized though.

CSS Optimization

-83%

Potential reduce by 22.7 kB

  • Original 27.5 kB
  • After minification 22.4 kB
  • After compression 4.8 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. Uglyparis.com needs all CSS files to be minified and compressed as it can save up to 22.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (39%)

Requests Now

23

After Optimization

14

  • Images
  • CSS

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

Network Requests Diagram

uglyparis.com

uglyparis.com

573 ms

www.uglyparis.com

www.uglyparis.com

700 ms

styles.css

styles.css

668 ms

0.jpg

0.jpg

302 ms

0.gif

0.gif

907 ms

0.jpg

0.jpg

304 ms

fv009.jpg

fv009.jpg

2487 ms

tables.css

tables.css

182 ms

box_top.png

box_top.png

167 ms

h1.jpg

h1.jpg

342 ms

box_body.png

box_body.png

354 ms

header.jpg

header.jpg

882 ms

h3.jpg

h3.jpg

546 ms

h3_r.jpg

h3_r.jpg

562 ms

rank1_a.gif

rank1_a.gif

516 ms

arrow_orange.gif

arrow_orange.gif

531 ms

rank2_a.gif

rank2_a.gif

681 ms

rank3_a.gif

rank3_a.gif

708 ms

point.png

point.png

729 ms

whats_top.jpg

whats_top.jpg

937 ms

whats_body.jpg

whats_body.jpg

855 ms

whats_li.jpg

whats_li.jpg

885 ms

whats_bottom.jpg

whats_bottom.jpg

910 ms

line.gif

line.gif

1019 ms

box_bottom.png

box_bottom.png

1058 ms

Accessibility Review

uglyparis.com accessibility score

89

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

Links do not have a discernible name

Best Practices

uglyparis.com best practices score

67

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

uglyparis.com SEO score

92

Search Engine Optimization Advices

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

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

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

uglyparis.com

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