Tools & Wizards About Us
curamess.com screenshot

Report Summary

  • 0

    Performance

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

curamess.com

陇南鄙段物流有限公司

Page Load Speed

2.7 sec in total

First Response

481 ms

Resources Loaded

1.8 sec

Page Rendered

400 ms

curamess.com screenshot

About Website

Welcome to curamess.com homepage info - get ready to check Curamess best content right away, or after learning these important things about curamess.com

陇南鄙段物流有限公司

Visit curamess.com

Key Findings

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

curamess.com performance score

0

Network Requests Diagram

curamess.com

481 ms

main.css

114 ms

layout.css

119 ms

font.css

125 ms

web.js.81df69f80213857d0c7a.js

60 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Curamess.com, 28% (23 requests) were made to Maps.googleapis.com and 11% (9 requests) were made to Image.jimcdn.com. The less responsive or slowest element that took the longest time to load (565 ms) relates to the external source Image.jimcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (61%)

Content Size

1.8 MB

After Optimization

694.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Curamess.com main page is 1.8 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. 70% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 60.9 kB

  • Original 85.9 kB
  • After minification 83.1 kB
  • After compression 25.0 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 60.9 kB or 71% of the original size.

Image Optimization

-3%

Potential reduce by 4.5 kB

  • Original 179.4 kB
  • After minification 174.9 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. Curamess images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 852.7 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 445.2 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 852.7 kB or 66% of the original size.

CSS Optimization

-75%

Potential reduce by 149.1 kB

  • Original 198.3 kB
  • After minification 198.0 kB
  • After compression 49.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. Curamess.com needs all CSS files to be minified and compressed as it can save up to 149.1 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (55%)

Requests Now

75

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

curamess.com

curamess.com

481 ms

main.css

main.css

114 ms

layout.css

layout.css

119 ms

font.css

font.css

125 ms

web.js.81df69f80213857d0c7a.js

web.js.81df69f80213857d0c7a.js

60 ms

image.png

image.png

140 ms

plusone.js

plusone.js

177 ms

25ca21cdac83090b6c335ebe5eaa50580e9f0c47

25ca21cdac83090b6c335ebe5eaa50580e9f0c47

252 ms

ga.js

ga.js

122 ms

analytics.js

analytics.js

161 ms

header.jpg

header.jpg

109 ms

web_oldtemplate.css.2d44259dc7097634303898168c3a0804.css

web_oldtemplate.css.2d44259dc7097634303898168c3a0804.css

66 ms

maxmess-software-im-igz-wernigerode.jpg

maxmess-software-im-igz-wernigerode.jpg

122 ms

rathaus-wernigerode.jpg

rathaus-wernigerode.jpg

120 ms

fachwerkstadt-wernigerode.jpg

fachwerkstadt-wernigerode.jpg

162 ms

image.png

image.png

247 ms

image.jpg

image.jpg

565 ms

image.png

image.png

247 ms

image.jpg

image.jpg

160 ms

all.js

all.js

293 ms

js

js

76 ms

ea80ec5a2c965c54340a933005e22d9d.woff

ea80ec5a2c965c54340a933005e22d9d.woff

12 ms

__utm.gif

__utm.gif

49 ms

__utm.gif

__utm.gif

49 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

29 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

65 ms

fastbutton

fastbutton

189 ms

common.js

common.js

49 ms

map.js

map.js

51 ms

util.js

util.js

53 ms

marker.js

marker.js

49 ms

geocoder.js

geocoder.js

48 ms

geometry.js

geometry.js

48 ms

directions.js

directions.js

49 ms

poly.js

poly.js

49 ms

collect

collect

46 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

200 ms

postmessageRelay

postmessageRelay

181 ms

onion.js

onion.js

140 ms

openhand_8_8.cur

openhand_8_8.cur

131 ms

infowindow.js

infowindow.js

99 ms

css

css

98 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

75 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

76 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

177 ms

stats.js

stats.js

63 ms

controls.js

controls.js

63 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

167 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

171 ms

rpc:shindig_random.js

rpc:shindig_random.js

169 ms

186 ms

transparent.png

transparent.png

97 ms

xd_arbiter.php

xd_arbiter.php

166 ms

xd_arbiter.php

xd_arbiter.php

287 ms

spotlight-poi.png

spotlight-poi.png

53 ms

google4.png

google4.png

57 ms

mapcnt6.png

mapcnt6.png

57 ms

sv5.png

sv5.png

57 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

48 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

22 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

22 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

21 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

23 ms

tmapctrl.png

tmapctrl.png

44 ms

tmapctrl4.png

tmapctrl4.png

22 ms

imgs8.png

imgs8.png

23 ms

vt

vt

67 ms

vt

vt

63 ms

vt

vt

47 ms

vt

vt

70 ms

vt

vt

65 ms

vt

vt

42 ms

vt

vt

81 ms

collect

collect

33 ms

loginstate

loginstate

204 ms

datepicker-de.5a100930ba3913ee1f2c.js

datepicker-de.5a100930ba3913ee1f2c.js

25 ms

ping

ping

26 ms

image.gif

image.gif

23 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

239 ms

like.php

like.php

64 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

290 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

324 ms

Accessibility Review

curamess.com accessibility score

71

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

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

curamess.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

curamess.com SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Curamess.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Curamess.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

curamess.com

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