Tools & Wizards About Us
weihsin.tw screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

weihsin.tw

Welcome to Haarlem Campus | Study in the Netherlands

Page Load Speed

19.1 sec in total

First Response

2.3 sec

Resources Loaded

11.3 sec

Page Rendered

5.6 sec

weihsin.tw screenshot

About Website

Click here to check amazing Weihsin content. Otherwise, check out these important facts you probably never knew about weihsin.tw

Haarlem Campus in the Netherlands offers Bachelor of Sciences degrees in Business Psychology, Digital Transformation and Creative Media.

Visit weihsin.tw

Key Findings

We analyzed Weihsin.tw page load time and found that the first response time was 2.3 sec and then it took 16.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

weihsin.tw performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value26,310 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.129

82/100

15%

TTI (Time to Interactive)

Value36.5 s

0/100

10%

Network Requests Diagram

weihsin.tw

2268 ms

xoops.css

863 ms

xoops.css

456 ms

bootstrap.css

1507 ms

bootstrap-responsive.css

1099 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 99% of them (123 requests) were addressed to the original Weihsin.tw, 1% (1 request) were made to Chart.apis.google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Weihsin.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (58%)

Content Size

1.7 MB

After Optimization

723.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weihsin.tw main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 909.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 39.8 kB

  • Original 49.0 kB
  • After minification 43.6 kB
  • After compression 9.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 5.4 kB, which is 11% 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 39.8 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 8.3 kB

  • Original 475.9 kB
  • After minification 467.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. Weihsin images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 714.3 kB

  • Original 909.2 kB
  • After minification 670.6 kB
  • After compression 194.9 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 714.3 kB or 79% of the original size.

CSS Optimization

-83%

Potential reduce by 251.1 kB

  • Original 302.6 kB
  • After minification 244.7 kB
  • After compression 51.5 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. Weihsin.tw needs all CSS files to be minified and compressed as it can save up to 251.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 95 (79%)

Requests Now

121

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weihsin.tw

weihsin.tw

2268 ms

xoops.css

xoops.css

863 ms

xoops.css

xoops.css

456 ms

bootstrap.css

bootstrap.css

1507 ms

bootstrap-responsive.css

bootstrap-responsive.css

1099 ms

font-awesome.css

font-awesome.css

1113 ms

style.css

style.css

663 ms

custom.css

custom.css

709 ms

xoops.js

xoops.js

995 ms

script.js

script.js

794 ms

browse.php

browse.php

1608 ms

jquery-migrate.min.js

jquery-migrate.min.js

1087 ms

shCore.js

shCore.js

1179 ms

shAutoloader.js

shAutoloader.js

1057 ms

jquery.mousewheel-3.0.6.pack.js

jquery.mousewheel-3.0.6.pack.js

1059 ms

jquery.fancybox.js

jquery.fancybox.js

1438 ms

jquery.fancybox-buttons.js

jquery.fancybox-buttons.js

1431 ms

jquery.fancybox-thumbs.js

jquery.fancybox-thumbs.js

1436 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

1431 ms

image.js

image.js

1436 ms

jquery.animated.innerfade.js

jquery.animated.innerfade.js

1477 ms

jscroller.js

jscroller.js

1506 ms

jquery.raty.js

jquery.raty.js

1492 ms

jquery-ui.js

jquery-ui.js

2244 ms

style.css

style.css

1624 ms

shCore.css

shCore.css

1651 ms

shThemeMonokai.css

shThemeMonokai.css

1682 ms

jquery.fancybox.css

jquery.fancybox.css

1710 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

1717 ms

jquery.fancybox-thumbs.css

jquery.fancybox-thumbs.css

1820 ms

iconize.css

iconize.css

1842 ms

jquery.ui.all.css

jquery.ui.all.css

1873 ms

colorbox.css

colorbox.css

1916 ms

jquery.colorbox.js

jquery.colorbox.js

1947 ms

jquery.pin.js

jquery.pin.js

2019 ms

reset.css

reset.css

2041 ms

responsiveslides.css

responsiveslides.css

1988 ms

responsiveslides.js

responsiveslides.js

2041 ms

block.css

block.css

1881 ms

bootstrap.js

bootstrap.js

2969 ms

jquery.ui.base.css

jquery.ui.base.css

218 ms

jquery.ui.theme.css

jquery.ui.theme.css

221 ms

jquery.ui.core.css

jquery.ui.core.css

223 ms

jquery.ui.accordion.css

jquery.ui.accordion.css

227 ms

jquery.ui.autocomplete.css

jquery.ui.autocomplete.css

224 ms

jquery.ui.button.css

jquery.ui.button.css

222 ms

jquery.ui.datepicker.css

jquery.ui.datepicker.css

222 ms

jquery.ui.dialog.css

jquery.ui.dialog.css

262 ms

jquery.ui.menu.css

jquery.ui.menu.css

590 ms

jquery.ui.progressbar.css

jquery.ui.progressbar.css

590 ms

jquery.ui.resizable.css

jquery.ui.resizable.css

430 ms

jquery.ui.selectable.css

jquery.ui.selectable.css

590 ms

jquery.ui.slider.css

jquery.ui.slider.css

590 ms

jquery.ui.spinner.css

jquery.ui.spinner.css

590 ms

jquery.ui.tabs.css

jquery.ui.tabs.css

635 ms

jquery.ui.tooltip.css

jquery.ui.tooltip.css

626 ms

chart

chart

339 ms

610 ms

logo_2_4.png

logo_2_4.png

339 ms

slide_2_1.jpg

slide_2_1.jpg

340 ms

slide_2_2.jpg

slide_2_2.jpg

338 ms

slide_2_3.jpg

slide_2_3.jpg

330 ms

48_m_7777.jpg

48_m_7777.jpg

329 ms

47_m_6666.jpg

47_m_6666.jpg

594 ms

46_m_5555.jpg

46_m_5555.jpg

590 ms

45_m_4444.jpg

45_m_4444.jpg

590 ms

44_m_3333.jpg

44_m_3333.jpg

582 ms

43_m_2222.jpg

43_m_2222.jpg

582 ms

42_m_1111.jpg

42_m_1111.jpg

773 ms

2leftarrow_g.png

2leftarrow_g.png

774 ms

1leftarrow_g.png

1leftarrow_g.png

774 ms

1rightarrow_g.png

1rightarrow_g.png

775 ms

2rightarrow_g.png

2rightarrow_g.png

774 ms

51_m_3333.jpg

51_m_3333.jpg

864 ms

comment_edit.png

comment_edit.png

1172 ms

2.jpg

2.jpg

1172 ms

glyphicons-halflings.png

glyphicons-halflings.png

308 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

508 ms

show.php

show.php

464 ms

post.php

post.php

467 ms

bg1.png

bg1.png

444 ms

foot.jpg

foot.jpg

329 ms

module.css

module.css

1127 ms

jcarousellite_1.0.1.min.js

jcarousellite_1.0.1.min.js

1255 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

333 ms

jquery.jgrowl.js

jquery.jgrowl.js

301 ms

previous.gif

previous.gif

1312 ms

pause.gif

pause.gif

1330 ms

next.gif

next.gif

1174 ms

overlay.png

overlay.png

280 ms

themes.gif

themes.gif

1330 ms

reload.png

reload.png

1212 ms

s01.gif

s01.gif

1243 ms

s02.gif

s02.gif

1244 ms

s03.gif

s03.gif

1244 ms

s04.gif

s04.gif

1244 ms

s05.gif

s05.gif

1244 ms

s06.gif

s06.gif

1230 ms

s07.gif

s07.gif

1230 ms

s08.gif

s08.gif

1230 ms

s09.gif

s09.gif

1230 ms

s10.gif

s10.gif

1230 ms

s11.gif

s11.gif

1231 ms

s12.gif

s12.gif

1283 ms

s13.gif

s13.gif

1261 ms

s14.gif

s14.gif

1261 ms

s15.gif

s15.gif

1262 ms

s16.gif

s16.gif

1261 ms

s17.gif

s17.gif

1261 ms

s18.gif

s18.gif

1262 ms

s19.gif

s19.gif

1246 ms

s20.gif

s20.gif

1245 ms

s21.gif

s21.gif

1245 ms

s22.gif

s22.gif

1290 ms

s23.gif

s23.gif

1291 ms

s24.gif

s24.gif

1292 ms

s25.gif

s25.gif

1291 ms

s26.gif

s26.gif

1292 ms

s27.gif

s27.gif

1312 ms

s28.gif

s28.gif

1234 ms

s29.gif

s29.gif

1355 ms

s30.gif

s30.gif

1336 ms

imageNavLeft.gif

imageNavLeft.gif

463 ms

imageNavRight.gif

imageNavRight.gif

325 ms

Accessibility Review

weihsin.tw accessibility score

95

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

weihsin.tw 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

SEO Factors

weihsin.tw SEO score

91

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

Links do not have descriptive text

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

    ZH

  • Encoding

    UTF-8

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

weihsin.tw

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